All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Jiri Benc <jbenc@suse.cz>,
	linux-wireless@vger.kernel.org, Guido Guenther <agx@sigxcpu.org>,
	at76c503a-develop@lists.berlios.de
Subject: Re: at76_usb - fourth submission attempt
Date: Thu, 23 Aug 2007 16:58:51 -0400	[thread overview]
Message-ID: <20070823205851.GK2989@tuxdriver.com> (raw)
In-Reply-To: <1184265547.29486.2.camel@dv>

On Thu, Jul 12, 2007 at 02:39:07PM -0400, Pavel Roskin wrote:
> On Thu, 2007-07-12 at 20:17 +0200, Jiri Benc wrote:

> > > 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.
> > 
> > Unfortunately, that prevents being accepted to vanilla.
> > 
> > I'd suggest to convert the driver to mac80211 and submit it then;
> > otherwise people will tend to look at the code saying "NAK, it contains
> > its own home grown 802.11 stack" only and not to review the driver in
> > depth.
> 
> Well, that make sense.  Helpers are welcome :)

I have added this to the 'at76' branch of wireless-dev, and attempted
to directly recruit some help to get this driver ported to mac80211.
I think that is a requirement for merging upstream, but at least
being in wireless-dev and -mm will get you some visibility, testing,
feedback, etc...

Thanks!

John
-- 
John W. Linville
linville@tuxdriver.com

      reply	other threads:[~2007-08-23 21:15 UTC|newest]

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

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=20070823205851.GK2989@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=agx@sigxcpu.org \
    --cc=at76c503a-develop@lists.berlios.de \
    --cc=jbenc@suse.cz \
    --cc=linux-wireless@vger.kernel.org \
    --cc=proski@gnu.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 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.