From: Greg KH <gregkh@linuxfoundation.org>
To: Pontus Fuchs <pontus.fuchs@gmail.com>
Cc: linux-wireless@vger.kernel.org, hch@lst.de, s.L-H@gmx.de
Subject: Re: [PATCH 0/4] Driver for the ar5523 chipset
Date: Fri, 12 Oct 2012 05:31:12 +0900 [thread overview]
Message-ID: <20121011203112.GB3317@kroah.com> (raw)
In-Reply-To: <1349985702-21322-1-git-send-email-pontus.fuchs@gmail.com>
On Thu, Oct 11, 2012 at 10:01:38PM +0200, Pontus Fuchs wrote:
> Some time ago I found an old USB wireless dongle in my drawer. I was
> surprised it wasn't supported in Linux. Google gave me an old
> unfinished driver created by Christoph Hellwig. Armed with some
> spare time and naivity I picked up where Christoph left in 2007 and
> now it's actually working pretty fine. It does not crash for me and
> throughput is decent.
>
> It's based on the FreeBSD driver, which in turn is based on the
> reverse engineered Windows driver, hence a very limited feature set.
> Not even HW crypto offload is supported. But at least there is a
> firmware which has a suitable license:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/dev/uath/ar5523.bin.uu
>
> Pontus Fuchs (4):
> ar5523: Add main driver file
> ar5523: Add driver header file
> ar5523: Add Firmware API header file
> ar5523: Add Kconfig and Makefile
>
> drivers/staging/Kconfig | 2 +
> drivers/staging/Makefile | 1 +
> drivers/staging/ar5523/Kconfig | 7 +
> drivers/staging/ar5523/Makefile | 1 +
> drivers/staging/ar5523/ar5523.c | 1824 ++++++++++++++++++++++++++++++++++++
> drivers/staging/ar5523/ar5523.h | 164 ++++
> drivers/staging/ar5523/ar5523_hw.h | 447 +++++++++
> 7 files changed, 2446 insertions(+)
> create mode 100644 drivers/staging/ar5523/Kconfig
> create mode 100644 drivers/staging/ar5523/Makefile
> create mode 100644 drivers/staging/ar5523/ar5523.c
> create mode 100644 drivers/staging/ar5523/ar5523.h
> create mode 100644 drivers/staging/ar5523/ar5523_hw.h
Very nice.
But what is keeping this driver from going to the "proper" place in the
kernel tree (i.e. drivers/net/...)? I don't have a problem adding it to
the staging tree, but it would need a TODO file to list what is needed
to get it out of the staging tree.
thanks,
greg k-h
next prev parent reply other threads:[~2012-10-11 20:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 20:01 [PATCH 0/4] Driver for the ar5523 chipset Pontus Fuchs
2012-10-11 20:01 ` [PATCH 1/4] ar5523: Add main driver file Pontus Fuchs
2012-10-15 20:54 ` Luis R. Rodriguez
2012-10-11 20:01 ` [PATCH 2/4] ar5523: Add driver header file Pontus Fuchs
2012-10-13 5:41 ` Kalle Valo
2012-10-13 10:14 ` Pontus Fuchs
2012-10-13 15:45 ` Christoph Hellwig
2012-10-21 19:58 ` Kalle Valo
2012-10-11 20:01 ` [PATCH 3/4] ar5523: Add Firmware API " Pontus Fuchs
2012-10-11 20:01 ` [PATCH 4/4] ar5523: Add Kconfig and Makefile Pontus Fuchs
2012-10-11 20:31 ` Greg KH [this message]
2012-10-12 6:52 ` [PATCH 0/4] Driver for the ar5523 chipset Pontus Fuchs
2012-10-12 7:28 ` Mohammed Shafi
2012-10-12 8:36 ` Pontus Fuchs
2012-10-12 8:23 ` Julian Calaby
2012-10-12 8:33 ` Pontus Fuchs
2012-10-12 11:45 ` Chadd, Adrian
2012-10-30 17:08 ` Adrian Chadd
2012-11-01 17:41 ` Pontus Fuchs
2012-10-12 7:11 ` Kalle Valo
2012-10-12 14:33 ` John W. Linville
2012-10-13 5:38 ` Kalle Valo
2012-10-13 10:25 ` Pontus Fuchs
2012-10-21 16:35 ` Kalle Valo
2012-10-13 15:41 ` Christoph Hellwig
2012-10-13 15:39 ` Christoph Hellwig
2012-10-22 22:43 ` Greg KH
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=20121011203112.GB3317@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linux-wireless@vger.kernel.org \
--cc=pontus.fuchs@gmail.com \
--cc=s.L-H@gmx.de \
/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.