From: Marek Vasut <marex@denx.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Chaoming Li <chaoming_li@realsil.com.cn>
Subject: Re: [PATCH] rtlwifi: rtl8192cu: Add new device ID
Date: Thu, 26 Mar 2015 02:13:42 +0100 [thread overview]
Message-ID: <201503260213.42322.marex@denx.de> (raw)
In-Reply-To: <551357F3.4020406@lwfinger.net>
On Thursday, March 26, 2015 at 01:50:59 AM, Larry Finger wrote:
> On 03/25/2015 04:18 PM, Marek Vasut wrote:
> > Add new ID for ASUS N10 WiFi dongle.
> >
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Larry Finger <Larry.Finger@lwfinger.net>
> > Cc: John W. Linville <linville@tuxdriver.com>
> > Cc: Chaoming Li <chaoming_li@realsil.com.cn>
> > ---
> >
> > drivers/net/wireless/rtlwifi/rtl8192cu/sw.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > Bus 001 Device 004: ID 0b05:17ba ASUSTek Computer, Inc.
> >
> > Device Descriptor:
> > bLength 18
> > bDescriptorType 1
> > bcdUSB 2.00
[...]
> > diff --git a/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
> > b/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c index 90a714c..d451d2b
> > 100644
> > --- a/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
> > +++ b/drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
> > @@ -360,6 +360,7 @@ static struct usb_device_id rtl8192c_usb_ids[] = {
> >
> > {RTL_USB_DEVICE(0x04f2, 0xaffb, rtl92cu_hal_cfg)}, /*Xavi*/
> > {RTL_USB_DEVICE(0x04f2, 0xaffc, rtl92cu_hal_cfg)}, /*Xavi*/
> > {RTL_USB_DEVICE(0x2019, 0x1201, rtl92cu_hal_cfg)}, /*Planex-Vencer*/
> >
> > + {RTL_USB_DEVICE(0x0b05, 0x17ba, rtl92cu_hal_cfg)}, /*ASUS-Edimax*/
> >
> > /****** 8192CU ********/
> > {RTL_USB_DEVICE(0x050d, 0x1004, rtl92cu_hal_cfg)}, /*Belcom-SurfN300*/
Hi!
> The full dump from lsusb is a bit much for a commit message. All you need
> is the one line from lsusb with no switches set.
That's why I added it below the diffstat, so that it doesn't polute the commit
message.
> According to the Vendor driver, which the comment indicates as the source
> of part of your patch,
In fact, the comment came from that same source file, from 0b05:17ab line.
The vendor is the same though, so I kept the comment.
> this particular device belongs in the "Customer ID"
> section under 8188CU, not where you placed it. In addition, I like to keep
> the USB IDs in numerical order within each section. Accordingly, your new
> ID should be between 0846:9041 and 0bda:5088.
OK.
> I am assuming that you have such a device. A statement that this change
> allows it to work should be in the commit message. If you have not tested,
> then you need to state that.
I have one and I tested it, I mostly checked the other commit messages and
wrote the same thing. It's a rather mindless change afterall.
next prev parent reply other threads:[~2015-03-26 1:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 21:18 [PATCH] rtlwifi: rtl8192cu: Add new device ID Marek Vasut
2015-03-26 0:50 ` Larry Finger
2015-03-26 1:13 ` Marek Vasut [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-19 13:51 Adrien Schildknecht
2015-08-19 14:12 ` Larry Finger
2015-08-19 14:27 ` Adrien Schildknecht
2015-08-19 14:42 ` Larry Finger
2014-01-09 16:27 Larry Finger
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=201503260213.42322.marex@denx.de \
--to=marex@denx.de \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=linux-kernel@vger.kernel.org \
--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 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).