All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Krause" <Martin.Krause@tqs.de>
To: "Larry Finger" <Larry.Finger@lwfinger.net>
Cc: <linux-wireless@vger.kernel.org>,
	"John Linville" <linville@tuxdriver.com>
Subject: AW: [PATCH] Staging: rtl8712: Change double device ID back to original value
Date: Fri, 2 Mar 2012 09:57:23 +0100	[thread overview]
Message-ID: <47F3F98010FF784EBEE6526EAAB078D10FD7EF81@tq-mailsrv.tq-net.de> (raw)
In-Reply-To: <4F4BA81D.1070800@lwfinger.net>

Hi Larry,

Larry Finger wrote on :
> On 02/27/2012 04:29 AM, Martin Krause wrote:
>> In the rtl8712 staging driver the 0bda:8172 usb device id exists two
>> times. It seems that this was an error when integrating the original
>> Realtek driver into the kernel. This patch changes the double device
>> id back to the value used in the last Realtek driver
>> (rtl8712_8188_8191_8192SU_usb_linux_v2.6.6.0.20110401).
>> 
>> Signed-off-by: Martin Krause<martin.krause@tqs.de>
>> ---
>> I tested this patch on a powerpc board (p2020 based) with a WIFIHU
>> Radicom wireless module with a RTL8191SU chip on it (usb device id
>> 0bda:8192). 
>> 
>>   drivers/staging/rtl8712/usb_intf.c |    2 +-
>>   1 files changed, 1 insertions(+), 1 deletions(-)
> 
> Your patch does two things. One is the deletion of a
> duplicate USB ID, and the
> other is the addition of a new one. I would prefer that any
> patch do one or the
> other, but not both. Note, there are two sets of duplicate
> IDs in the table for
> the driver - the one you note in the RTL8191SU section, and another
> for 0bda:8174 in the section that covers the RTL8192SU.
> 
> I think you are deleting the wrong 0bda:8172 with this patch.
> The 0bda code is
> for Realtek, thus the one in the Asus section is the one to remove.
> 
> Does your chip really have an RTL8191SU label? The USB
> database says that ID
> 0bda:8192 is for the RTL8192SU. I would like to correct the database
> if it is wrong.

>From the Radicom engineers I get the following answer:

"Our WiFiHU is using RTL8191SU and USB ID is 0BDA/8192".

It seems the USB database is wrong, so. And this might be also an
explanation why this USB ID is used in the rtl8192su staging driver
(file drivers\staging\rtl8192u\r8192U_core.c). I compiled this driver
during my tests with the embedded Radicum WIFIHU wireless module
and it accepts this USB id (0bda:8192), but it did not work with
it. In contrast, the rtl8712 staging driver is working with this
moudule if adding this USB ID to it (as done in my patch).

Regards,
Martin

>> diff --git a/drivers/staging/rtl8712/usb_intf.c
> b/drivers/staging/rtl8712/usb_intf.c
>> index 9bade18..bb247ce 100644
>> --- a/drivers/staging/rtl8712/usb_intf.c
>> +++ b/drivers/staging/rtl8712/usb_intf.c
>> @@ -104,7 +104,7 @@ static struct usb_device_id rtl871x_usb_id_tbl[]
>> = { 
>> 
>>   /* RTL8191SU */
>>   	/* Realtek */
>> -	{USB_DEVICE(0x0BDA, 0x8172)},
>> +	{USB_DEVICE(0x0BDA, 0x8192)},
>>   	/* Amigo */
>>   	{USB_DEVICE(0x0EB0, 0x9061)},
>>   	/* ASUS/EKB */

      parent reply	other threads:[~2012-03-02  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 10:29 [PATCH] Staging: rtl8712: Change double device ID back to original value Martin Krause
2012-02-27 15:58 ` Larry Finger
2012-02-27 17:14   ` AW: " Martin Krause
2012-03-02  8:57   ` Martin Krause [this message]

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=47F3F98010FF784EBEE6526EAAB078D10FD7EF81@tq-mailsrv.tq-net.de \
    --to=martin.krause@tqs.de \
    --cc=Larry.Finger@lwfinger.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.