From: Mahesh Kuruganti <maheshkuruganti@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] ZTEAC8710 Support with Device ID 0xffff
Date: Tue, 13 Apr 2010 16:03:11 +0530 [thread overview]
Message-ID: <z2ned984c71004130333t5a9534beqac5269f8e5fb4b88@mail.gmail.com> (raw)
In-Reply-To: <x2led984c71004130329l3a531dag88242427583d5a78@mail.gmail.com>
Here is a patch in the correct format compiled against
Linux-2.6.34-rc3.Also I tested it and it compiled with no problem and
I am using it now as i type.
PATCH TO EXTEND SUPPORT TO AC8710 WITH 0xFFFF Product ID.
--- drivers/usb/serial/option.c.orig 2010-04-12 21:44:55.902548876 +0530
+++ drivers/usb/serial/option.c 2010-04-12 21:51:47.302549297 +0530
@@ -304,6 +304,8 @@ static int option_resume(struct usb_ser
#define ZTE_PRODUCT_CDMA_TECH 0xfffe
#define ZTE_PRODUCT_AC8710 0xfff1
#define ZTE_PRODUCT_AC2726 0xfff5
+//There seems to be an Alternate Device ID for the AC8710 supplied in India.
+#define ZTE_PRODUCT_AC8710T 0xffff
#define BENQ_VENDOR_ID 0x04a5
#define BENQ_PRODUCT_H10 0x4068
@@ -677,6 +679,7 @@ static const struct usb_device_id option
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x0141, 0xff, 0xff, 0xff) },
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID,
ZTE_PRODUCT_CDMA_TECH, 0xff, 0xff, 0xff) },
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID,
ZTE_PRODUCT_AC8710, 0xff, 0xff, 0xff) },
+ { USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID,
ZTE_PRODUCT_AC8710T, 0xff, 0xff, 0xff) },
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID,
ZTE_PRODUCT_AC2726, 0xff, 0xff, 0xff) },
{ USB_DEVICE(BENQ_VENDOR_ID, BENQ_PRODUCT_H10) },
{ USB_DEVICE(DLINK_VENDOR_ID, DLINK_PRODUCT_DWM_652) },
Signed-off-by: Mahesh Kuruganti <maheshkuruganti@gmail.com>
--
Mahesh Kuruganti
parent reply other threads:[~2010-04-13 10:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <x2led984c71004130329l3a531dag88242427583d5a78@mail.gmail.com>]
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=z2ned984c71004130333t5a9534beqac5269f8e5fb4b88@mail.gmail.com \
--to=maheshkuruganti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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).