linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Claudio <der.claudio@aon.at>,
	linux-wireless@vger.kernel.org, Greg KH <gregkh@suse.de>
Subject: Re: status of at76-usb driver
Date: Tue, 6 Jan 2009 15:15:17 -0500	[thread overview]
Message-ID: <20090106201517.GD3544@tuxdriver.com> (raw)
In-Reply-To: <87fxk8o2g0.fsf@litku.valot.fi>

On Sun, Dec 28, 2008 at 03:26:55PM +0200, Kalle Valo wrote:

> Fortunately Greg created staging tree some time ago and included the
> original at76_usb driver to the tree:
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree;f=drivers/staging/at76_usb;hb=HEAD
> 
> So starting from 2.6.28 (please correct me if I'm wrong here) the
> original (and working!) at76_usb driver should be included already in
> the kernel, it's just up to the distributions to enable it.
> 
> Grep, I noticed that the TODO file in your tree doesn't mention
> anything about my mac80211 port. I'll send you a patch fixing that.
> 
> 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.

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?

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

  parent reply	other threads:[~2009-01-06 20:30 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 [this message]
2009-01-07  6:04     ` Kalle Valo
2009-01-08 14:56       ` Claudio
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=20090106201517.GD3544@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=der.claudio@aon.at \
    --cc=gregkh@suse.de \
    --cc=kalle.valo@iki.fi \
    --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 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).