linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: linux-wireless@vger.kernel.org
Cc: Guido Guenther <agx@sigxcpu.org>, at76c503a-develop@lists.berlios.de
Subject: at76_usb - fourth submission attempt
Date: Thu, 12 Jul 2007 04:16:06 -0400	[thread overview]
Message-ID: <1184228166.2377.31.camel@dv> (raw)

Hello!

I'd like to submit at76_usb driver for inclusion into the kernel.

The driver's temporary repository is located at
http://git.80211libre.org/at76_usb.git/

To compile the driver standalone, just run "make" and "make install".
To integrate the driver into the kernel, apply kernel_patch.diff to the
kernel with -p1 option, then copy at76_usb*.[ch] to drivers/net/wireless

For the driver to work, please download the firmware from
http://developer.berlios.de/projects/at76c503a/

This is the fourth submission attempt.  Three previous attempts were
made by Guido Guenther, and generated a lot of useful feedback.  I
believe all the recommendations have been accepted.

The driver went through a massive cleanup, but I realize that a lot of
work still needs to be done.  I think the process will be more effective
if more people take a look at the code.  New eyes will see new flaws.

The biggest change that has not been done is conversion to mac80211.  I
believe it's possible, but I don't expect it to happen overnight.  Until
then, at76_usb uses its own implementation of 802.11 protocol.  I'm not
going to polish it, but I tried to clean up the code to the point that
it can be easily understood.

If possible, I'd like the driver to be in Linux 2.6.23.  That would
rejuvenate the interest to the driver, and hopefully it might attract
new contributors.  I think at76_usb is quite on the par with other
non-mac80211 drivers currently in Linux (although I do realize that it's
a poor excuse).

I'll do my best to convert the driver to mac80211.  I think it would be
OK to replace the driver with the mac80211 version later, e.g. in Linux
2.6.24.  There are parts of the driver that don't deal with 802.11 layer
(e.g. firmware download and MIBs), and it would be great if they receive
some good testing in the meantime.

In any case, I'll appreciate any comments regarding the code.

It's my first driver submission ever, so please don't hesitate to tell
me if I'm doing anything wrong.

-- 
Regards,
Pavel Roskin


             reply	other threads:[~2007-07-12  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  8:16 Pavel Roskin [this message]
2007-07-12 10:00 ` at76_usb - fourth submission attempt Johannes Berg
2007-07-12 18:17 ` Jiri Benc
2007-07-12 18:39   ` Pavel Roskin
2007-08-23 20:58     ` John W. Linville

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=1184228166.2377.31.camel@dv \
    --to=proski@gnu.org \
    --cc=agx@sigxcpu.org \
    --cc=at76c503a-develop@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).