linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
To: Larry Finger <Larry.Finger@lwfinger.net>,
	Matthew Garrett <mjg@redhat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	herton@mandriva.com.br, linux-wireless@vger.kernel.org,
	flamingice@sourmilk.net, andreamrl@tiscali.it,
	linville@redhat.com
Subject: Re: [RFC][PATCH] Realtek 8187B wireless support with product id 0x8197/0x8189
Date: Thu, 26 Jun 2008 00:44:55 +0000 (GMT)	[thread overview]
Message-ID: <779389.39286.qm@web23108.mail.ird.yahoo.com> (raw)
In-Reply-To: <20080626002645.GB2618@srcf.ucam.org>

--- On Thu, 26/6/08, Matthew Garrett <mjg@redhat.com> wrote:
<snipped>
> One thing I noticed is that the 0x8187 USB ID seems to be
> used for both 
> plain and b devices, so I suspect we're going to need
> some more 
> intelligent probing than just basing it off USB ID. IIRC,
> the endpoint 
> descriptions are different?

This is my /proc/bus/usb/devices entry- anybody who has a 0x8187 which 
behaves like a 8187b posting theirs? You remember correctly - 8187 
sends through endpoint 2, 8187b uses 4,5,6,7 and 12 (0x0c). 
----------
T:  Bus=01 Lev=01 Prnt=01 Port=05 Cnt=01 Dev#=  2 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0bda ProdID=8197 Rev= 2.00
S:  Manufacturer=Manufacturer_Realtek
S:  Product=RTL8187B_WLAN_Adapter 
S:  SerialNumber=<masked>
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:* If#= 0 Alt= 0 #EPs= 9 Cls=ff(vend.) Sub=ff Prot=ff Driver=rtl8187
E:  Ad=83(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=05(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=06(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=07(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=89(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=0a(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=0b(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=0c(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
------------


      __________________________________________________________
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

  reply	other threads:[~2008-06-26  0:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-15  0:59 [RFC][PATCH] Realtek 8187B wireless support with product id 0x8197/0x8189 Hin-Tak Leung
2008-06-18 22:31 ` Uwe Hermann
2008-06-19  0:17   ` Hin-Tak Leung
2008-06-25 14:08 ` John W. Linville
2008-06-25 14:59   ` Larry Finger
2008-06-25 15:44     ` Hin-Tak Leung
2008-06-26  0:26     ` Matthew Garrett
2008-06-26  0:44       ` Hin-Tak Leung [this message]
2008-06-26  3:41         ` Larry Finger
2008-06-26 17:22           ` Hin-Tak Leung
2008-06-26 18:33             ` Larry Finger
2008-06-26 18:44               ` Pavel Roskin
2008-06-26 19:45                 ` Hin-Tak Leung
2008-06-26 20:40                   ` Herton Ronaldo Krzesinski
2008-06-26 21:24                     ` Herton Ronaldo Krzesinski
2008-06-26 21:53                       ` Larry Finger
2008-06-26 20:44                   ` Larry Finger
2008-06-26 21:15                     ` Herton Ronaldo Krzesinski

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=779389.39286.qm@web23108.mail.ird.yahoo.com \
    --to=hintak_leung@yahoo.co.uk \
    --cc=Larry.Finger@lwfinger.net \
    --cc=andreamrl@tiscali.it \
    --cc=flamingice@sourmilk.net \
    --cc=herton@mandriva.com.br \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@redhat.com \
    --cc=linville@tuxdriver.com \
    --cc=mjg@redhat.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).