From: Claudio <der.claudio@aon.at>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: "\"John W. Linville\"" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, Greg KH <gregkh@suse.de>
Subject: Re: status of at76-usb driver
Date: Thu, 08 Jan 2009 15:56:44 +0100 (CET) [thread overview]
Message-ID: <1231426604.4966142c2f17c@webmail.aon.at> (raw)
In-Reply-To: <da94abde0901062204r1041cdeawf0a0360cad88741d@mail.gmail.com>
Kalle Valo <kalle.valo@iki.fi> wrote:
> On Tue, Jan 6, 2009 at 10:15 PM, John W. Linville
> <linville@tuxdriver.com> wrote:
>> On Sun, Dec 28, 2008 at 03:26:55PM +0200, Kalle Valo wrote:
>>
>>> Also I\'m going to rename the mac80211 port to something else for just
>>> to avoid the confusion with the original driver. Last thing I want to
>>> see is having two in-tree drivers with identical names.
>>
>> OK, I still have patches to recreate the original port of at76_usb
>> to mac80211 and another to keep-up with a later mac80211 API change
>> on the at76 branch of wireless-testing. I had intended to send them
>> to Greg now that the mac80211 API change has made it upstream.
>
> I have to disagree here. It\'s better not to change at76_usb in staging
> to avoid any breakage. Like I said, I will submit the mac80211 port
> with a new name (most probably at76c50x-usb) as soon as I get it
> stable enough. It\'s good idea to have a working driver in staging tree
> until the mac80211 has been verified to be working.
I think so too.
>> Since you mentioned a) that you are working on the port again and b)
>> you are going to rename the driver for mac80211, should I just drop
>> my at76 branch of wireless testing for good?
>
> Please do, because I will submit at7650x-usb patches from scratch. But
> don\'t remove at76 branch from the legacy tree, it\'s useful for me:
I am looking forward for testing your new mac80211 version. Please tell
me where the development happens, so that I can contribute to it.
Regarding Ubuntu: They are still shipping an ancient version (0.14beta1!).
Sorry for considering blaming you for the problems. The current version
of the staging-tree/directory(?) works well.
Claudio
next prev parent reply other threads:[~2009-01-08 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 20:51 status of at76-usb driver Claudio
2008-12-28 13:26 ` Kalle Valo
2008-12-28 21:28 ` Pavel Roskin
2008-12-29 0:33 ` Greg KH
2008-12-29 6:13 ` Kalle Valo
2008-12-30 13:52 ` Claudio
2009-01-02 15:53 ` Kalle Valo
2009-01-02 19:12 ` Claudio
2009-01-02 19:55 ` Kalle Valo
2009-01-06 20:15 ` John W. Linville
2009-01-07 6:04 ` Kalle Valo
2009-01-08 14:56 ` Claudio [this message]
2009-01-08 16:33 ` Kalle Valo
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=1231426604.4966142c2f17c@webmail.aon.at \
--to=der.claudio@aon.at \
--cc=gregkh@suse.de \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 NNTP newsgroup(s).