linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Andrea Merello <andrea.merello@gmail.com>
Cc: wlanfae@realtek.com, shwei <shwei@realtek.com.tw>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <greg@kroah.com>,
	linux-wireless@vger.kernel.org,
	Michael Wu <flamingice@sourmilk.net>
Subject: Re: RTL8187SE staging Linux driver
Date: Tue, 10 Sep 2013 12:56:06 -0400	[thread overview]
Message-ID: <20130910165606.GB1960@tuxdriver.com> (raw)
In-Reply-To: <CAN8YU5NTKUtS8+YzmcOSM3=YUX-FSwLTD86F_hXsNdVkw5NEGA@mail.gmail.com>

On Tue, Sep 10, 2013 at 05:59:54PM +0200, Andrea Merello wrote:
> Hello,
> 
> As you probably know, in the current Linux kernel there is a staging
> driver for the RTL8187SE device (based on my older RTL8180/RTL8185
> Linux driver), while there also a regular (not staging) driver
> supporting older RTL8185 and RTL8180 devices
> (net/wireless/rtl818x/rtl8180) .
> 
> As far as I can see, the RTL8187SE device seems not so much different
> from an RTL8185 device.
> I would like to try (in my spare time) to add support for RTL8187SE
> device in the current RTL818x driver, in order to avoid code
> duplication, remove a driver from staging, and make RTL8187SE using
> mac80211.
> 
> Do any one of you have any comment/objection/suggestions about this ?

I would be extremely happy for you to tackle this.

> Is it possible to get the RTL8187SE documentation to make things easier?

This info used to be readily available.  If you can't find a source, I
probably still have a (mildly useful) datasheet somewhere in my heap...

> For now I will probably keep different RF code for the two cards even
> if the RTL8225 (zebra 2) radio is used by both RTL8187SE and some
> RTL8185 devices, however if I could get enough documentation about it,
> it would be great to try to merge also RF code..
> 
> Thank you,
> Andrea

Seems reasonable...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2013-09-10 17:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 15:59 RTL8187SE staging Linux driver Andrea Merello
2013-09-10 16:56 ` John W. Linville [this message]
2013-09-10 17:35 ` Larry Finger
2013-09-11  6:11   ` Andrea Merello
2014-01-14 17:40     ` Andrea Merello
2014-01-14 21:50       ` Larry Finger
2014-01-15 16:11       ` Larry Finger
2014-01-15 17:22         ` Andrea Merello
2014-01-15 17:42           ` Larry Finger
2014-01-15 18:41             ` Andrea Merello
2014-01-15 18:43               ` Andrea Merello
2014-01-15 20:29                 ` Larry Finger
2014-01-20 21:48         ` Andrea Merello

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=20130910165606.GB1960@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=andrea.merello@gmail.com \
    --cc=flamingice@sourmilk.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shwei@realtek.com.tw \
    --cc=wlanfae@realtek.com \
    /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).