From: Peter Hicks <peter.hicks@poggs.co.uk>
To: Nils Radtke <lkml@Think-Future.de>
Cc: linux-kernel@vger.kernel.org
Subject: RE: option.ko: ZTE MF636 support
Date: Sun, 09 May 2010 22:55:32 +0100 [thread overview]
Message-ID: <1273442132.12665.28.camel@angel> (raw)
In-Reply-To: <20100509142209.GA9319@localhost>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
Hi Nils
On Sun, 2010-05-09 at 16:22 +0200, Nils Radtke wrote:
> Similar symptoms are the long delay on opening of devices 0 and 2.
> /dev/ttyUSB0: status port
> /dev/ttyUSB2: modem port (not working)
Does "echo > /dev/ttyUSB0" return immediately, and "echo > /dev/ttyUSB2"
take around 15 seconds to return?
> What has been your solution to get the ZTE working?
I've blacklisted devices 0, 1 and 2 using the attached patch, taken
against 2.6.34-rc6. It should be quite straightforward to modify this
for your device.
Without the patch, I'm able to use wvdial against ttyUSB3 to dial up,
but the device is unresponsive to anything apart from a PPP LCP
disconnect.
Regards,
Peter
[-- Attachment #2: zte-mf636-blacklist.patch --]
[-- Type: text/x-patch, Size: 1350 bytes --]
--- drivers/usb/serial/option.orig.c 2010-05-09 22:46:41.761498988 +0100
+++ drivers/usb/serial/option.c 2010-05-09 22:44:49.911498986 +0100
@@ -393,6 +393,13 @@
.reason = OPTION_BLACKLIST_SENDSETUP
};
+static const u8 zte_mf636_no_sendsetup[] = { 0, 1, 2 };
+static const struct option_blacklist_info zte_mf636_blacklist = {
+ .infolen = ARRAY_SIZE(zte_mf636_no_sendsetup),
+ .ifaceinfo = zte_mf636_no_sendsetup,
+ .reason = OPTION_BLACKLIST_SENDSETUP
+};
+
static const struct usb_device_id option_ids[] = {
{ USB_DEVICE(OPTION_VENDOR_ID, OPTION_PRODUCT_COLT) },
{ USB_DEVICE(OPTION_VENDOR_ID, OPTION_PRODUCT_RICOLA) },
@@ -609,7 +616,9 @@
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x0030, 0xff, 0xff, 0xff) },
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, ZTE_PRODUCT_MF626, 0xff, 0xff, 0xff) },
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x0032, 0xff, 0xff, 0xff) },
- { USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x0033, 0xff, 0xff, 0xff) },
+ { USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x0033, 0xff, 0xff, 0xff),
+ .driver_info = (kernel_ulong_t)&zte_mf636_blacklist
+ },
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x0037, 0xff, 0xff, 0xff) },
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x0039, 0xff, 0xff, 0xff) },
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x0042, 0xff, 0xff, 0xff) },
next prev parent reply other threads:[~2010-05-09 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 13:27 option.ko: ZTE MF636 support Peter Hicks
2010-05-09 14:22 ` Nils Radtke
2010-05-09 21:55 ` Peter Hicks [this message]
2010-05-10 11:45 ` Nils Radtke
2010-05-11 8:40 ` 2.6.34-rc7 option.c: support for olicard100 + zte636-0x0037 Nils Radtke
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=1273442132.12665.28.camel@angel \
--to=peter.hicks@poggs.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@Think-Future.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