From: Kalle Valo <kvalo@adurom.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [TODO] at76c50x: remove wext includes
Date: Sat, 16 Jul 2011 14:41:38 +0300 [thread overview]
Message-ID: <87vcv2v4el.fsf@purkki.adurom.net> (raw)
In-Reply-To: <4E1DA3A0.1000606@gnu.org> (Pavel Roskin's message of "Wed\, 13 Jul 2011 09\:54\:40 -0400")
Pavel Roskin <proski@gnu.org> writes:
> On 07/13/2011 04:52 AM, Kalle Valo wrote:
>> The driver has been broken due to the mac80211 changes for a long time
>> and it's obvious that I can't maintain it anymore as I haven't touched
>> it for a long time. I would like to just remove it altogether. Any
>> objections?
>>
>> If someone wants to step up and fix it, now is the time to do it.
>
> Please keep the driver for now!
Ok, I won't remove it now but I'll send a patch stating that it's
broken currently.
> I have a pile of compatible hardware, and I should be able to fix
> it. I'm placing it onto my TODO list.
Nice. Thank you for stepping in.
> There is some really obsolete hardware that we may need to stop
> supporting, e.g. Atheros AR5210, but the reason is because it's
> supported by an actively developed driver, ath5k, and the AR5210 code
> stands in the way all the time.
>
> However, at76c50x-usb is a separate driver and it doesn't stand in the
> way of anybody except when global changes are made.
You are right. The problem is that the driver is broken currently as
it requires bssid before authentication and mac80211 doesn't provide
it. Or at least I haven't found a way to do that.
I know that Johannes has been talking about adding support for
providing bssid to the driver before authentication. So there is a
chance that we might be able to fix this without major hacks.
--
Kalle Valo
prev parent reply other threads:[~2011-07-16 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 8:47 [TODO] at76c50x: remove wext includes Johannes Berg
2011-07-13 8:52 ` Kalle Valo
2011-07-13 10:35 ` Julian Calaby
2011-07-13 10:50 ` Kalle Valo
2011-07-13 11:15 ` Julian Calaby
2011-07-13 13:54 ` Pavel Roskin
2011-07-16 11:41 ` Kalle Valo [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=87vcv2v4el.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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 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 NNTP newsgroup(s).