From: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>
To: Greg KH <greg@kroah.com>
Cc: smurf@smurf.noris.de, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb-serial: option: Don't match Huawei driver CD images
Date: Fri, 18 Apr 2008 08:01:34 +0200 [thread overview]
Message-ID: <1208498494.14194.28.camel@hermes2.karcher.local> (raw)
In-Reply-To: <20080418032405.GB8754@kroah.com>
Am Donnerstag, den 17.04.2008, 20:24 -0700 schrieb Greg KH:
> What is this patch against? We have a change that went into 2.6.25
> after 2.6.25-rc9 that should make this patch not be needed.
The patch is developed against 2.6.25-rc8 + some git patches, but I have
forward-ported it to current git.
I *guess* you are talking about commit aad8a278 (USB: support more
Huawei data card product IDs), as I could not find . The header of this
patch talks about three changes (declaration of unusual devices,
disabling product ID matching in driver.c and finally declaring the
product in option.c). I find only the first and the last point if this
reflected in the patch, and there are *no* patches at all to
drivers/usb/core/driver.c in the timeframe you mentioned. This patch
addresses the second point of that list, but in another way.
The problem is that those huawei products have four USB interfaces,
three usb-serial like interfaces handled by the option driver and a
fourth one to be handled by usb-storage. When the stick gets initially
plugged, only the mass storage device is visible and needs a magic kick
to expose the other interfaces. aad8a278 contains a valid and working
patch to kick those USB devices if the mass storage interface gets bound
by usb-storage. At least in 2.6.25-rc8, if the option module is loaded,
the mass storage device gets bound to the option driver instead that
exposes a useless and non-functional serial interface on the mass
storage endpoint. This prevents the usb-storage driver to perform the
needed kicking.
> Can you try that release and verify this?
I will try with a current git kernel without my patch and report back,
but I will be surprised if the problem described above is gone. System
is currently compiling.
> thanks,
You're welcome.
Kind regards,
Michael Karcher
next prev parent reply other threads:[~2008-04-18 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 22:49 Michael Karcher
2008-04-18 3:24 ` Greg KH
2008-04-18 6:01 ` Michael Karcher [this message]
2008-04-18 6:30 ` Michael Karcher
2008-05-28 17:17 ` Greg KH
2008-05-28 21:58 ` Michael Karcher
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=1208498494.14194.28.camel@hermes2.karcher.local \
--to=kernel@mkarcher.dialup.fu-berlin.de \
--cc=greg@kroah.com \
--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®