All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] wifi: move raycs, wl3501 and rndis_wlan to legacy directory
Date: Mon, 27 Feb 2023 21:11:30 +0200	[thread overview]
Message-ID: <87ilfmrkil.fsf@kernel.org> (raw)
In-Reply-To: <cc905b745580b0300d10f1f88d714305c7544f67.camel@redhat.com> (Dan Williams's message of "Mon, 27 Feb 2023 12:09:06 -0600")

Dan Williams <dcbw@redhat.com> writes:

> On Mon, 2023-02-27 at 14:17 +0200, Kalle Valo wrote:
>> To clean up drivers/net/wireless move the old drivers drivers left in
>> the
>> directory to a new "legacy" directory. I did consider adding
>> CONFIG_WLAN_VENDOR_LEGACY like other vendors have but then dropped
>> the idea as
>> these are really old drivers and hopefully we get to remove them
>> soon.
>
> Why is rndis_wlan legacy? It supports devices that are way newer than
> ray_cs or wl3501... like this Linksys WUSB54GSC from late 2007:
>
> [1086339.589565] rndis_wlan 1-3:1.0 wlan0: register 'rndis_wlan' at
> usb-0000:00:14.0-3, Wireless RNDIS device, BCM4320b based,
> 00:1d:7e:9e:2f:bb
> [1086339.589961] usbcore: registered new interface driver rndis_wlan

So you have this device? Does it work? I think I should make a table
somewhere for these old drivers with last success reports :)

> Dunno, just seems a completely different class of devices than old
> 802.11b-only PCMCIA ones...

I was about to say that all drivers using Wireless Extensions are
legacy, but to my surprise rndis_wlan actually uses cfg80211 :)

I put this to "legacy" as I didn't find any better location and adding a
new vendor driver just for rndis_wlan felt like overkill. The directory
name "legacy" is just a name, it has no real meaning and users won't see
it either. It could be "misc", "old" or something else as well.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2023-02-27 19:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 12:17 [PATCH 0/2] wifi: create legacy and virtual directories Kalle Valo
2023-02-27 12:17 ` [PATCH 1/2] wifi: move mac80211_hwsim and virt_wifi to virtual directory Kalle Valo
2023-03-13 13:42   ` Kalle Valo
2023-02-27 12:17 ` [PATCH 2/2] wifi: move raycs, wl3501 and rndis_wlan to legacy directory Kalle Valo
2023-02-27 17:50   ` kernel test robot
2023-02-27 19:14     ` Kalle Valo
2023-02-27 18:09   ` Dan Williams
2023-02-27 19:11     ` Kalle Valo [this message]
2023-02-27 21:01       ` Dan Williams
2023-02-28  6:29         ` Kalle Valo
2023-02-28 17:37           ` Dan Williams
2023-03-01  7:09             ` Kalle Valo
2023-03-01 16:33               ` Dan Williams

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=87ilfmrkil.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.