From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Greg KH <greg@kroah.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"otus-devel@lists.madwifi-project.org"
<otus-devel@lists.madwifi-project.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Release of Atheros 802.11n USB Linux driver
Date: Thu, 23 Oct 2008 04:11:03 -0700 [thread overview]
Message-ID: <20081023111103.GB5979@tesla> (raw)
In-Reply-To: <20081023062655.GA8039@kroah.com>
On Wed, Oct 22, 2008 at 11:26:55PM -0700, Greg KH wrote:
> On Tue, Oct 21, 2008 at 11:50:45PM -0700, Greg KH wrote:
> > On Tue, Oct 21, 2008 at 07:04:17PM -0700, Luis R. Rodriguez wrote:
> > > We would like to see our Atheros 802.11n USB Linux driver upstream
> > > however we need help with this so we are releasing our Atheros 11n USB
> > > Otus Linux driver under the ISC to the community. The goal is to work
> > > with the community to help move this forward upstream. We are hoping
> > > for community help and leadership on this (*cough*).
> >
> > Yeah!
> >
> > I'll grab this and put it in drivers/staging/ so it gets some users and
> > more developers to help out with it.
>
> Ok, it seems to need some basic work to merely build properly on
> "modern" kernel versions.
Yeah, it works up to 2.6.24.
> So, how should we do this if I want to move it into staging? Can I just
> take a snapshot of what you have in this repo, move it in-kernel, fix
> the build errors and apply that patch (as your contribution of course)?
That's the thing it needs Wireless Extension support for >= 2.6.24 so
that needs to be done. I can try to do it but first comes ath9k, hence
why we released it to engage with the community on adding that and to
eventually push it upstream.
> Then future development can go off of the in-kernel version? Or do you
> plan to keep this git tree active somehow?
Yeah so the purpose of the git tree is to collect patches to allow users
to use it with >= 2.6.24, all other focus should be on an in-kernel
driver.
Luis
WARNING: multiple messages have this Message-ID (diff)
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Greg KH <greg@kroah.com>
Cc: Luis Rodriguez <Luis.Rodriguez@atheros.com>,
"otus-devel@lists.madwifi-project.org"
<otus-devel@venema.h4ckr.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Release of Atheros 802.11n USB Linux driver
Date: Thu, 23 Oct 2008 04:11:03 -0700 [thread overview]
Message-ID: <20081023111103.GB5979@tesla> (raw)
In-Reply-To: <20081023062655.GA8039@kroah.com>
On Wed, Oct 22, 2008 at 11:26:55PM -0700, Greg KH wrote:
> On Tue, Oct 21, 2008 at 11:50:45PM -0700, Greg KH wrote:
> > On Tue, Oct 21, 2008 at 07:04:17PM -0700, Luis R. Rodriguez wrote:
> > > We would like to see our Atheros 802.11n USB Linux driver upstream
> > > however we need help with this so we are releasing our Atheros 11n USB
> > > Otus Linux driver under the ISC to the community. The goal is to work
> > > with the community to help move this forward upstream. We are hoping
> > > for community help and leadership on this (*cough*).
> >
> > Yeah!
> >
> > I'll grab this and put it in drivers/staging/ so it gets some users and
> > more developers to help out with it.
>
> Ok, it seems to need some basic work to merely build properly on
> "modern" kernel versions.
Yeah, it works up to 2.6.24.
> So, how should we do this if I want to move it into staging? Can I just
> take a snapshot of what you have in this repo, move it in-kernel, fix
> the build errors and apply that patch (as your contribution of course)?
That's the thing it needs Wireless Extension support for >= 2.6.24 so
that needs to be done. I can try to do it but first comes ath9k, hence
why we released it to engage with the community on adding that and to
eventually push it upstream.
> Then future development can go off of the in-kernel version? Or do you
> plan to keep this git tree active somehow?
Yeah so the purpose of the git tree is to collect patches to allow users
to use it with >= 2.6.24, all other focus should be on an in-kernel
driver.
Luis
next prev parent reply other threads:[~2008-10-23 18:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 2:04 Release of Atheros 802.11n USB Linux driver Luis R. Rodriguez
2008-10-22 6:50 ` Greg KH
2008-10-23 6:26 ` Greg KH
2008-10-23 6:26 ` Greg KH
2008-10-23 11:11 ` Luis R. Rodriguez [this message]
2008-10-23 11:11 ` Luis R. Rodriguez
2008-10-27 23:35 ` [otus-devel] " Luis R. Rodriguez
2008-10-27 23:35 ` Luis R. Rodriguez
2008-10-28 0:29 ` Greg KH
2008-10-28 0:29 ` Greg KH
2008-10-28 0:55 ` Luis R. Rodriguez
2008-10-28 0:55 ` Luis R. Rodriguez
2008-10-28 5:56 ` Greg KH
2008-10-28 5:56 ` Greg KH
2008-10-28 14:17 ` Joerg Albert
2008-10-28 14:17 ` Joerg Albert
2008-10-28 5:54 ` Joey Krane
2008-10-28 5:54 ` Joey Krane
2008-10-28 13:24 ` Joerg Albert
2008-10-28 13:24 ` Joerg Albert
2008-10-28 15:18 ` Greg KH
2008-10-28 15:18 ` Greg KH
2008-10-22 8:28 ` Florian Fainelli
2008-10-22 8:28 ` Florian Fainelli
2008-10-22 16:13 ` Luis R. Rodriguez
2008-10-22 16:13 ` Luis R. Rodriguez
2008-10-22 10:05 ` Michael Renzmann
2008-10-23 23:37 ` Luis R. Rodriguez
2008-10-23 23:37 ` Luis R. Rodriguez
2008-10-24 6:28 ` [otus-devel] " Michael Renzmann
2008-10-24 6:28 ` Michael Renzmann
2008-10-24 13:41 ` Joerg Albert
2008-10-24 13:41 ` Joerg Albert
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=20081023111103.GB5979@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=otus-devel@lists.madwifi-project.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.