From: "John W. Linville" <linville@tuxdriver.com>
To: Frederic Leroy <fredo@starox.org>
Cc: Hin-Tak Leung <hintak.leung@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
Chris Mayo <aklhfex@googlemail.com>,
linux-wireless@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: staging: No option to select rtl8192su in linux-2.6.33-rc2
Date: Sat, 13 Feb 2010 19:40:10 -0500 [thread overview]
Message-ID: <20100214004010.GB18815@tuxdriver.com> (raw)
In-Reply-To: <20100213234456.5ae49b67@houba>
On Sat, Feb 13, 2010 at 11:44:56PM +0100, Frederic Leroy wrote:
> Le Thu, 31 Dec 2009 14:38:35 +0000,
> Hin-Tak Leung <hintak.leung@gmail.com> a écrit :
>
> > "nobody cares" is not entirely true - AFAIK, code in the staging area
> > is unreliable/unsuitable/"poor" code which serves the sole purpose of
> > being there for scavenging and references for re-write (because there
> > is no equivalent functionality, even alleged, in mainline); so people
> > looking at the staging code for ideas or references is welcomed. It is
> > just that there is no hints of any support or vague guarantee that any
> > of it works for any fitness of purpose. i.e. patches which fix
> > problems, or migrate functionality out of the staging area to
> > main-line, are welcomed, but questions and request for help on
> > understanding or making any of it work, are not.
>
> I just bought an wireless usb key based on realtek 8192. If nobody is
> working on making a driver for it, I'd like to try.
>
> But I am wondering where/how to start.
>
> Should I follow the TODO file from Greg in staging :
> ( which seems to merge : rtl8192e rtl8192su rtl8192u )
>
> TODO:
> - prepare private ieee80211 stack for merge with rtl8187se's version:
> - remove rtl8192su's specific dead code
> - cleanup ieee80211.h
> - move rtl8192su's specific code out from ieee80211.h
> - abstract rtl819su's specific code
> - use list_for_each_safe() in ieee80211_crypto_deinit
> - switch to use shared "librtl" instead of private ieee80211 stack
> - switch to use LIB80211
> - switch to use MAC80211
> - switch to use EEPROM_93CX6
> - use kernel coding style
> - checkpatch.pl fixes
> - sparse fixes
> - integrate with drivers/net/wireless/rtl818x
This is a reasonable plan overall, although I might quibble with
the order.
> Or use rtl818x tree to start a new device ?
YMMV, but given the code I've seen for the Realtek drivers in staging I
might be inclined to start by forking rtl8180 and making the necessary
hardware changes from there.
Hth!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-02-14 1:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 12:20 staging: No option to select rtl8192su in linux-2.6.33-rc2 Chris Mayo
2009-12-28 21:59 ` Marcel Holtmann
2009-12-31 14:38 ` Hin-Tak Leung
2010-02-13 22:44 ` Frederic Leroy
2010-02-14 0:40 ` John W. Linville [this message]
2010-02-14 12:18 ` Frederic Leroy
2010-02-14 17:21 ` Larry Finger
2010-02-14 17:44 ` Frederic Leroy
2010-02-17 0:44 ` Hin-Tak Leung
2010-02-17 8:17 ` Frederic Leroy
2010-02-17 16:37 ` Larry Finger
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=20100214004010.GB18815@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=aklhfex@googlemail.com \
--cc=fredo@starox.org \
--cc=greg@kroah.com \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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.