public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: "Paweł Drobek" <pawel.drobek@gmail.com>
Cc: Greg KH <greg@kroah.com>,
	Linux USB list <linux-usb@vger.kernel.org>,
	Linux-kernel <linux-kernel@vger.kernel.org>,
	Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: option driver, ZTE MF_330 matches linux usb 2.0 root hub
Date: Fri, 27 May 2011 10:19:42 +0400	[thread overview]
Message-ID: <4DDF427E.1030109@msgid.tls.msk.ru> (raw)
In-Reply-To: <BANLkTikcjXTczV2FmGcQ7BY=m_t7ep54Sw@mail.gmail.com>

27.05.2011 09:40, Paweł Drobek wrote:
> I have got device with this ID's and you are right ID2 is usb2 hub id
> but when you put my device into computer with this settings my device
> report it self as gsm modem based on option.ko module. as far i know
> there are no other solution to get working zte 330 on linux.

Can you please provide the information Greg asked?

>     I don't know, Paweł, can you provide the output of 'lsusb -v' for your
>     system where you saw this being a option device instead of a hub?

Namely, `lsusb -v' output from the system when this
modem is inserted.

At least, maybe this device ID should be restricted to
the particular class of devices.  Alternatively, if number
of such devices on the marked is small (google wasn't able
to find any other references), it should be easy to control
it using a custom udev rule that loads `option' driver and
forcibly binds it to this device.  That is, by the way, an
alternative solution to make it work.

But it is curious that ZTE used "wrong" vendor class for
its product.

Thanks!

/mjt

  parent reply	other threads:[~2011-05-27  6:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 21:13 option driver, ZTE MF_330 matches linux usb 2.0 root hub Michael Tokarev
2011-05-26 21:28 ` Michael Tokarev
2011-05-27  1:20   ` Greg KH
     [not found]     ` <BANLkTikcjXTczV2FmGcQ7BY=m_t7ep54Sw@mail.gmail.com>
2011-05-27  6:19       ` Michael Tokarev [this message]
     [not found]         ` <BANLkTikodJ4cnjJ9Lxx=zsHd-dAgPzfDrA@mail.gmail.com>
2011-05-27  9:04           ` Michael Tokarev
     [not found]             ` <BANLkTi==1WyJNACmoOxcrS6RiJ3w8Ow1zw@mail.gmail.com>
2011-05-27 10:02               ` Greg KH
2011-05-27 13:19                 ` Michael Tokarev
     [not found]                   ` <BANLkTinAip5BswLBjxyJ1O_XPnUFq=FUjw@mail.gmail.com>
2011-05-27 20:30                     ` Greg KH
2011-06-06 13:21                     ` Michael Tokarev
     [not found]                       ` <BANLkTimLfkGjFtk_GJ87_+f7fswkdmSe3Q@mail.gmail.com>
2011-06-07  4:48                         ` Paweł Drobek
2011-06-07  6:35                           ` Michael Tokarev
2011-06-08 13:32                             ` Jiri Kosina

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=4DDF427E.1030109@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=pawel.drobek@gmail.com \
    /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