lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081023111103.GB5979@tesla>
Date:	Thu, 23 Oct 2008 04:11:03 -0700
From:	"Luis R. Rodriguez" <lrodriguez@...eros.com>
To:	Greg KH <greg@...ah.com>
CC:	Luis Rodriguez <Luis.Rodriguez@...eros.com>,
	"otus-devel@...ts.madwifi-project.org" 
	<otus-devel@...ts.madwifi-project.org>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	Linux-Kernel <linux-kernel@...r.kernel.org>,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: Release of Atheros 802.11n USB Linux driver

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ