All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Krause <martin.krause@tqs.de>
To: linville@example.com
Cc: linux-wireless@vger.kernel.org, Larry.Finger@lwfinger.net
Subject: [PATCH] Staging: rtl8712: Change double device ID back to original value
Date: Mon, 27 Feb 2012 11:29:56 +0100	[thread overview]
Message-ID: <20120227102857.21246.43090.stgit@localhost.localdomain> (raw)

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(-)

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 */


             reply	other threads:[~2012-02-27 10:39 UTC|newest]

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

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=20120227102857.21246.43090.stgit@localhost.localdomain \
    --to=martin.krause@tqs.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@example.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.