All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Leroy <fredo@starox.org>
To: "John W. Linville" <linville@tuxdriver.com>
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: Sun, 14 Feb 2010 13:18:10 +0100	[thread overview]
Message-ID: <20100214131810.1a8b49ac@houba> (raw)
In-Reply-To: <20100214004010.GB18815@tuxdriver.com>

Le Sat, 13 Feb 2010 19:40:10 -0500,
"John W. Linville" <linville@tuxdriver.com> a écrit :

> [...]
> > Should I follow the TODO file from Greg in staging :
> > ( which seems to merge : rtl8192e  rtl8192su  rtl8192u )
> > [...] 
> 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.
 
It was my impression too, but as you say, YMMV. It will be my first
driver, although I already hacked the kernel, make netfilters modules
and read lwn ;).

For the process, it is still unclear for me. I copy rtl8180*[ch] to
rtl8192*[ch], and start to hack into to make clean git patches ?

On which tree should I base my work : 
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git ?

> hth!

It helps :)

-- 
Frédéric Leroy

  reply	other threads:[~2010-02-14 12:19 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
2010-02-14 12:18         ` Frederic Leroy [this message]
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=20100214131810.1a8b49ac@houba \
    --to=fredo@starox.org \
    --cc=aklhfex@googlemail.com \
    --cc=greg@kroah.com \
    --cc=hintak.leung@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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.