linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hin-Tak Leung <htl10@users.sourceforge.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Vinicius Piccoli <viniciuspiccoli@gmail.com>,
	herton@mandriva.com.br, linux-wireless@vger.kernel.org
Subject: Re: REALTEK 8187SE
Date: Sat, 12 Feb 2011 04:25:48 +0000	[thread overview]
Message-ID: <4D560BCC.7070104@users.sourceforge.net> (raw)
In-Reply-To: <4D55FC96.50305@lwfinger.net>

Larry Finger wrote:
> On 02/11/2011 08:44 PM, Vinicius Piccoli wrote:
>> Dear Friends
>>
>> I'm newbee in UBUNTU I have install 10.1 in my netbook, I have a 
>> realteck 8187SE,
>> but can not make the wireless work, do you guys have a driver of
>> sofwarecontroler for it?
>>
>> The LAN is working fine!
> 
> There is a driver in drivers/staging that has been there for quite a 
> while. I'm not sure what kernel it first appeared in, but I know it is 
> in 2.6.34. If Ubuntu does not enable it, then you will have either 
> change distros, or build your own kernel.
> 
> Larry
> 

According to wireless-testing's log, the first kernel which a version of the 
8187se staging driver is included is 2.6.29 .

The 8187se staging driver is essentially the same as the Realtek rtl8187se 
vendor driver which is available as a standard-alone download (i.e. without the 
rest of the kernel source tree, and build-able as such) from a variety of 
on-line places, not least Ubuntu's laundpad as attachment to a few 
bug/enhancement reports.

AFAIK, the 8187se is quite a different beast and uses the PCI interface and 
closer to the 8180/8185(?), rather than the USB interface like the 8187L/8187B.

However, I found a few issues concerning your e-mail problematic:

1) You have obviously worked out that the 3 of us are the current 8187/8187B 
maintainers, which suggests that you are not as newbie as you like us to believe 
- all the 8187se info are available in the linux-wireless mailing list archive, 
really, and you could have found the same info we gave you by similiar methods 
you found our e-mail addresses. I am not your friend. I really do not know you.

2) I can't speak for the others, but I generally do not like people e-mailing me 
  privately (i.e. without CC'ing a relevant mailing list) on reasonably widely 
applicable open-source issues. A private answer to a private question benefit 
nobody else. That's the purpose of having mailing lists and mailing list 
archives are for. If I want to receive e-mails from random unknown individuals 
privately, I would charge them for it.

Hin-Tak

           reply	other threads:[~2011-02-12  4:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4D55FC96.50305@lwfinger.net>]

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=4D560BCC.7070104@users.sourceforge.net \
    --to=htl10@users.sourceforge.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=herton@mandriva.com.br \
    --cc=linux-wireless@vger.kernel.org \
    --cc=viniciuspiccoli@gmail.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).