From: Peter Hicks <peter.hicks@poggs.co.uk>
To: linux-kernel@vger.kernel.org
Subject: option.ko: ZTE MF636 support
Date: Sat, 08 May 2010 14:27:38 +0100 [thread overview]
Message-ID: <1273325258.15521.38.camel@angel> (raw)
Hello
I've discovered that the ZTE MF636 USB HSUPA modem (USB ID 19d2:0033)
doesn't play well with option.ko. This seems to be a similar problem to
the 4G W14 stick (commit a74171005f2f6474e05bdfccb05c9f0d68224a49).
The symptom of this problem is that the first three serial ports on the
MF636 take around 10s to open with modem-manager, and fail to open with
Minicom. The fourth serial port is fine.
Blacklisting the first three interfaces in option.c results in them
opening immediately. This reduces modem detection time in modem-manager
from 20-30 seconds to around five.
As there is only a single blacklisted device in option.c at present,
what is the best way to work around this problem? Can somebody help me
with writing a patch to submit to fix the problem in the kernel?
Regards,
Peter
next reply other threads:[~2010-05-08 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 13:27 Peter Hicks [this message]
2010-05-09 14:22 ` option.ko: ZTE MF636 support Nils Radtke
2010-05-09 21:55 ` Peter Hicks
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=1273325258.15521.38.camel@angel \
--to=peter.hicks@poggs.co.uk \
--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