From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Christoph Hellwig <hch@lst.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org
Cc: Dan Williams <dcbw@redhat.com>, Jouni Malinen <j@w1.fi>,
Greg KH <greg@kroah.com>,
"John W. Linville" <linville@tuxdriver.com>,
devel@driverdev.osuosl.org, ath9k-devel@venema.h4ckr.net,
ath5k-devel@venema.h4ckr.net,
madwifi-devel <madwifi-devel@lists.sourceforge.net>
Subject: Re: AR5523 driver - old Atheros USB
Date: Tue, 21 Jul 2009 17:03:36 -0700 [thread overview]
Message-ID: <43e72e890907211703y72ffe8cdv88ba9e3c59d1b76@mail.gmail.com> (raw)
In-Reply-To: <20090721214219.GA25392@lst.de>
On Tue, Jul 21, 2009 at 2:42 PM, Christoph Hellwig<hch@lst.de> wrote:
> On Tue, Jul 21, 2009 at 02:24:36PM -0700, Luis R. Rodriguez wrote:
>> >> Hey Chris, was curious if you still had lying around the driver you
>> >> had worked on for the old Atheros 802.11 USB device. Dan asked about
>> >> it, seems he bought one. We at least now have specs for it and can
>> >> provide them to interested developers. Since Dan brought this device
>> >> up figured I'd check to see if you still had it to see if you still
>> >> had the code and might be willing to let someone try to give a shot at
>> >> finishing it up for inclusion. Perhaps staging?
>> >
>> > The code has been at http://verein.lst.de/~hch/ar5523.tgz.
>>
>> Sweet. How functional is this? Does it TX/RX?
>
> It's been quite some time. IIRC it does TX, but can't actually see
> any packets on RX (filter issue or something).
Sorry for the large cross post, just seeing if someone is interested
in working on a wireless driver. The task would be to try to get
AR5523 USB driver up to speed with mac80211 from wireless-testing and
giving it a shot to fix remaining issues?
It seems to have compiled last for 2.6.23.
If you're interested please remove all lists and only leave
linux-wireless on the reply.
Luis
parent reply other threads:[~2009-07-22 0:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20090721214219.GA25392@lst.de>]
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=43e72e890907211703y72ffe8cdv88ba9e3c59d1b76@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=dcbw@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=j@w1.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=madwifi-devel@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®