All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pontus Fuchs <pontus.fuchs@gmail.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, hch@lst.de, s.L-H@gmx.de,
	Pontus Fuchs <pontus.fuchs@gmail.com>
Subject: [PATCH v2 0/4] Driver for the ar5523 chipset
Date: Tue, 16 Oct 2012 21:29:25 +0200	[thread overview]
Message-ID: <1350415769-8271-1-git-send-email-pontus.fuchs@gmail.com> (raw)

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

Changes v1 to v2:

* Place driver in drivers/net/wireless/ath instead of staging.
* Change to same license as ath9k as suggested by Luis.
* Add comment about shutting up errors on USB disconnect.
* Use ALIGN() / IS_ALIGNED() for alignment fix / check.
* Fix whitespace on file ending.
* Bugfix: Avoid % 512 transfer sizes on TX as the FW will hang.
* Bugfix: Change filtering so that [mb]cast are properly RXed.

Pontus Fuchs (4):
  ar5523: Add main driver file
  ar5523: Add driver header file
  Add Firmware API header file
  Add Kconfig and Makefile. Add MAINTAINERS entry

 MAINTAINERS                                 |    6 +
 drivers/net/wireless/ath/Kconfig            |    1 +
 drivers/net/wireless/ath/Makefile           |    1 +
 drivers/net/wireless/ath/ar5523/Kconfig     |    7 +
 drivers/net/wireless/ath/ar5523/Makefile    |    1 +
 drivers/net/wireless/ath/ar5523/ar5523.c    | 1816 +++++++++++++++++++++++++++
 drivers/net/wireless/ath/ar5523/ar5523.h    |  155 +++
 drivers/net/wireless/ath/ar5523/ar5523_hw.h |  434 +++++++
 8 files changed, 2421 insertions(+)
 create mode 100644 drivers/net/wireless/ath/ar5523/Kconfig
 create mode 100644 drivers/net/wireless/ath/ar5523/Makefile
 create mode 100644 drivers/net/wireless/ath/ar5523/ar5523.c
 create mode 100644 drivers/net/wireless/ath/ar5523/ar5523.h
 create mode 100644 drivers/net/wireless/ath/ar5523/ar5523_hw.h

-- 
1.7.9.5


             reply	other threads:[~2012-10-16 19:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 19:29 Pontus Fuchs [this message]
2012-10-16 19:29 ` [PATCH v2 1/4] ar5523: Add main driver file Pontus Fuchs
2012-10-23 13:52   ` Christoph Hellwig
2012-10-16 19:29 ` [PATCH v2 2/4] ar5523: Add driver header file Pontus Fuchs
2012-10-16 19:29 ` [PATCH v2 3/4] Add Firmware API " Pontus Fuchs
2012-10-16 19:29 ` [PATCH v2 4/4] Add Kconfig and Makefile. Add MAINTAINERS entry Pontus Fuchs
2012-10-16 21:22 ` [PATCH v2 0/4] Driver for the ar5523 chipset Christian Lamparter
2012-10-18  8:48   ` Pontus Fuchs
2012-10-18  8:59 ` Hauke Mehrtens
2012-10-18 10:31   ` Pontus Fuchs
2012-10-23 13:51     ` Christoph Hellwig

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=1350415769-8271-1-git-send-email-pontus.fuchs@gmail.com \
    --to=pontus.fuchs@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.