All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	Michael Wu <flamingice@sourmilk.net>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: Problems with RTL8187 USB device
Date: Tue, 26 Feb 2008 22:27:16 -0700	[thread overview]
Message-ID: <47C4F4B4.7030300@gmail.com> (raw)
In-Reply-To: <20080227010732.GB3066@tuxdriver.com>

John W. Linville wrote:
> On Tue, Feb 26, 2008 at 04:13:37PM -0700, Larry Finger wrote:
>   
>> After the BCM4311 that is built-in on my laptop failed, I bought a USB wi-fi device to use until I
>> get my laptop fixed. Based on suggestions from the wireless mailing list, I bought one with an
>> RTL8187 chip. Naturally, I am having problems getting it working.
>>
>> First of all, the device works with Windows - thus it is OK.
>>
>> The device is manufactured by "Level 1". The FCC ID is NDD9573160714 and it has the identifying code
>> of WNC-0301USB07091001070-V5.
>>
>> The output of 'lsusb -v' for this device when run as root is
>>
>> Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp.
>>     
>
> This looks like it should be supported by the rtl8187 driver.
>
> <snip>
>
>   
>>   iProduct                2 RTL8187B_WLAN_Adapter
>>     
>
> <snip>
>
>   
>>         bEndpointAddress     0x83  EP 3 IN
>>     
>
> <snip>
>
> But these bits look like it is actually an rtl8187b, which is not
> supported by the driver.  I didn't know that there where some 'b'
> devices using the same USB ID as the non-b devices -- crappy vendor's
> strike again.  I'm not sure what to do about that one.
>
> As for rtl8187b support in general, I've been looking at porting
> support for those devices form the vendor-provided driver.  But the
> patch is incomplete ATM -- hopefully soon, depending on events. :-(
>
> I'm sorry you are caught in the middle.  I'll try to get that b support
> patch done soon -- hopefully we can get something working for you then.
>
>   
Thanks for the info.

If I can give you any help with the patch, please let me know. In about
another week, I will be forced to use Windows to access the Internet
(Yuck!!).

Larry


  reply	other threads:[~2008-02-27  5:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 23:13 Problems with RTL8187 USB device Larry Finger
2008-02-27  1:07 ` John W. Linville
2008-02-27  5:27   ` Larry Finger [this message]
2008-03-01 19:21     ` Larry Finger
2008-03-25 20:31   ` Daniel Gimpelevich
2008-04-01 15:41     ` Daniel Gimpelevich
2008-04-01 17:51       ` John W. Linville
2008-04-01 18:07         ` Daniel Gimpelevich
2008-04-01 18:24           ` [PATCH] rtl8187b work in progress John W. Linville
2008-04-02  0:09             ` Herton Ronaldo Krzesinski
2008-04-02  2:40               ` Herton Ronaldo Krzesinski
2008-04-04  3:33                 ` Pavel Roskin
2008-04-04 14:07                   ` Herton Ronaldo Krzesinski
2008-04-04 15:17                     ` Pavel Roskin
2008-04-07 12:01                       ` Herton Ronaldo Krzesinski
2008-04-04  3:21             ` Pavel Roskin
2008-04-01 21:26           ` Problems with RTL8187 USB device Pavel Roskin

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=47C4F4B4.7030300@gmail.com \
    --to=larry.finger@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=flamingice@sourmilk.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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 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.