From: "Hanno Böck" <hanno@hboeck.de>
To: smurf@smurf.noris.de
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] option.c: Support QUALCOMM iCON 210
Date: Sat, 27 Jun 2009 16:53:49 +0200 [thread overview]
Message-ID: <200906271653.49970.hanno@hboeck.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 697 bytes --]
Hi,
Attached is a patch for option.c to support the QUALCOMM HSDPA-Stick iCON 210.
There was an earlier patch (http://patchwork.kernel.org/patch/29709/) that
wasn't applied.
I was a bit unsure how to handle it as it contians not the known qualcomm
vendor id. Maybe it's from some third-party vendor, though it's unknown in
usb.ids.
I've named the variable QUALCOMM_ICON_VENDOR_ID, hope this is ok, else give me
feedback how to handle that.
Please apply. CC me on all answers, as I'm not subscribed to the mailing
lists.
cu,
--
Hanno Böck Blog: http://www.hboeck.de/
GPG: 3DBD3B20 Jabber/Mail: hanno@hboeck.de
http://schokokeks.org - professional webhosting
[-- Attachment #1.2: option-icon210.diff --]
[-- Type: text/x-diff, Size: 896 bytes --]
--- linux-2.6.30-crap/drivers/usb/serial/option.c 2009-06-10 05:05:27.000000000 +0200
+++ linux-2.6.30/drivers/usb/serial/option.c 2009-06-27 14:13:56.000000000 +0200
@@ -285,6 +285,9 @@
#define QUALCOMM_VENDOR_ID 0x05C6
+#define QUALCOMM_ICON_VENDOR_ID 0x1E0E
+#define QUALCOMM_ICON_PRODUCT_210 0x9000
+
#define MAXON_VENDOR_ID 0x16d8
#define TELIT_VENDOR_ID 0x1bc7
@@ -513,6 +516,7 @@
{ USB_DEVICE(KYOCERA_VENDOR_ID, KYOCERA_PRODUCT_KPC680) },
{ USB_DEVICE(QUALCOMM_VENDOR_ID, 0x6000)}, /* ZTE AC8700 */
{ USB_DEVICE(QUALCOMM_VENDOR_ID, 0x6613)}, /* Onda H600/ZTE MF330 */
+ { USB_DEVICE(QUALCOMM_ICON_VENDOR_ID, QUALCOMM_ICON_PRODUCT_210)}, /* Qualcomm iCON 210 */
{ USB_DEVICE(MAXON_VENDOR_ID, 0x6280) }, /* BP3-USB & BP3-EXT HSDPA */
{ USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_UC864E) },
{ USB_DEVICE(ZTE_VENDOR_ID, ZTE_PRODUCT_MF622) },
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2009-06-27 14:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200906271653.49970.hanno@hboeck.de \
--to=hanno@hboeck.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=smurf@smurf.noris.de \
/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
all inboxes | Powered by JetHome®