linux-kernel - Re: option driver, ZTE MF_330 matches linux usb 2.0 root hub

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 27 May 2011 10:19:42 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Paweł Drobek <pawel.drobek@...il.com>
CC:	Greg KH <greg@...ah.com>,
	Linux USB list <linux-usb@...r.kernel.org>,
	Linux-kernel <linux-kernel@...r.kernel.org>,
	Dominik Brodowski <linux@...inikbrodowski.net>
Subject: Re: option driver, ZTE MF_330 matches linux usb 2.0 root hub

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/