From: jim.cromie@gmail.com
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: "Larry.Finger@lwfinger.net" <Larry.Finger@lwfinger.net>,
Peter Robinson <pbrobinson@gmail.com>,
kernelnewbies@kernelnewbies.org
Subject: Re: How to switch driver from wireless extension to cfg/mac80211
Date: Fri, 13 Oct 2023 15:23:41 -0600 [thread overview]
Message-ID: <CAJfuBxz50=Ve0O+2FzPmExdL-DzvsypED1EL8CFmjAFP9TJjdQ@mail.gmail.com> (raw)
In-Reply-To: <a386389e-d388-4f78-b55e-5c1b15e34cfc@gmail.com>
On Sat, Oct 7, 2023 at 1:14 PM Philipp Hortmann
<philipp.g.hortmann@gmail.com> wrote:
>
> Hi,
>
> after cutting away a lot of dead code from the rtl8192e I would like to
> understand the way forward to migrate the driver from wireless extension
> to cfg/mac80211.
>
I think you need more email recipients for definitive answers.
In particular, is anyone else doing this ?
if they are, you should find them, make the job easier.
> What is the best way forward to migrate the driver rtl8192e towards the
> drivers/net/wireless/realtek/rtlwifi/rtl8192* ?
>
Id start with this search:
$ git log --grep=ieee80211_ -p -- drivers/net/wireless/realtek/ | less
+/ieee80211_
then narrow with a particular api-call that sounds like it would be central
to the switchover.
It might be useful to search for many api calls at once,
rank them by how many of the calls they add
(presuming more to be better, more "comprehensive")
> Does it have to be a hard cut?
not sure what you mean, but I'd guess no - smaller incremental changes
are preferred
>
> What to start with?
> - start to change the used structs towards ieee80211_hw?
the old adage: look at the data structs 1st.
not sure how well that applies in any given (or your) situation.
adapting old code to new structs does sound sane, and incrementally testable.
>
> Thanks for your support.
>
> Bye Philipp
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2023-10-13 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 19:12 How to switch driver from wireless extension to cfg/mac80211 Philipp Hortmann
2023-10-13 21:23 ` jim.cromie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJfuBxz50=Ve0O+2FzPmExdL-DzvsypED1EL8CFmjAFP9TJjdQ@mail.gmail.com' \
--to=jim.cromie@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=kernelnewbies@kernelnewbies.org \
--cc=pbrobinson@gmail.com \
--cc=philipp.g.hortmann@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).