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: Tue, 07 Jun 2011 10:35:58 +0400	[thread overview]
Message-ID: <4DEDC6CE.7080100@msgid.tls.msk.ru> (raw)
In-Reply-To: <1307422131.5615.3.camel@one.pl>

07.06.2011 08:48, Paweł Drobek wrote:

> Bus 003 Device 002: ID 19d2:0001 ONDA Communication S.p.A.
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               1.10
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0
>   bDeviceProtocol         0
>   bMaxPacketSize0        64
>   idVendor           0x19d2 ONDA Communication S.p.A.
>   idProduct          0x0001
>   bcdDevice            0.00
>   iManufacturer           1 Qualcomm, Incorporated
>   iProduct                2 ZTE CDMA Technologies MSM
>   iSerial                 0
>   bNumConfigurations      1
>   Configuration Descriptor:
>     bLength                 9
>     bDescriptorType         2
>     wTotalLength           85
>     bNumInterfaces          3
>     bConfigurationValue     1
>     iConfiguration          0
>     bmAttributes         0xa0
>       (Bus Powered)
>       Remote Wakeup
>     MaxPower              500mA
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           3
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass    255 Vendor Specific Subclass
>       bInterfaceProtocol    255 Vendor Specific Protocol
>       iInterface              3 Data Interface

So, as far as I can see, this is covered by

#define ZTE_VENDOR_ID                           0x19d2
#define ZTE_PRODUCT_MF622                       0x0001

{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, ZTE_PRODUCT_MF622, 0xff, 0xff, 0xff) }, /* ZTE WCDMA products */

and it should Just Work aftere reverting a559d2c8c1bf652ea2d0ecd6ab4a250fcdb37db8
"USB: option: add ID for ZTE MF 330".  But I'm not sure this really
is MF330, since the device ID says it's MF622.

Are we talking about the same device?

Besides, why in linux it's identified as ZTE, while
lsusb lists it as "ONDA Comm." ?

Thanks,

/mjt

  reply	other threads:[~2011-06-07  6:36 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
     [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 [this message]
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=4DEDC6CE.7080100@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