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>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 07 Jun 2011 06:48:51 +0200
From:	Paweł Drobek <pawel.drobek@...il.com>
To:	Michael Tokarev <mjt@....msk.ru>
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

Dnia 2011-06-06, pon o godzinie 15:36 +0200, Paweł Drobek pisze:
> Nope sorry, i got very busy week. Mayby tomorrow i could check id
> 
> sorry
> 
> W dniu 6 czerwca 2011 15:21 użytkownik Michael Tokarev
> <mjt@....msk.ru> napisał:
>         27.05.2011 17:24, Paweł Drobek wrote:
>         > On weekend i could give you all data which you need to do
>         more precisely
>         > action. Just write all command should i give.
>         
>         
>         Paweł, are there any news on this?
>         
>         Thanks,
>         
>         /mjt
>         
>         > 2011/5/27 Michael Tokarev <mjt@....msk.ru
>         <mailto:mjt@....msk.ru>>
>         
>         >
>         >     27.05.2011 14:02, Greg KH wrote:
>         >     > On Fri, May 27, 2011 at 11:06:37AM +0200, Paweł Drobek
>         wrote:
>         >     >> dunno, zte mf330 is pcmcia card identified itself as
>         usb device
>         >     which need to
>         >     >> get working pcmcia options from kernel.
>         >     >
>         >     > Yes, older devices put a whole USB host controller
>         device on the
>         >     PCMCIA
>         >     > card in order to talk to it properly without having to
>         change their
>         >     > hardware design of the modem chip.
>         >
>         >     So, what's our course of actions now?
>         >
>         >     I'd suggest to revert this change and deal with this
>         device
>         >     again (specifying the device IDs more precisely, like,
>         >     including the device class or what it is called in USB
>         >     world) when someone will have it for real.
>         >
>         >     Thanks,
>         >
>         >     /mjt
>         >
>         >
>         >
>         >
>         > --
>         > -----BEGIN GEEK CODE BLOCK-----
>         > Version: 3.12
>         > GCS d+ s:+ a- C++ UL++++ P L+++ !E W+++ N++ o+ K- w++
>         > !O M V- PS+ PE+ Y PGP++ !t !5 X++++ R+ tv- b++ DI++ D++
>         > G++ e+++ h+ r-- y
>         > ------END GEEK CODE BLOCK------
>         >
>         
>         
> 
> 
> 
> -- 
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.12
> GCS d+ s:+ a- C++ UL++++ P L+++ !E W+++ N++ o+ K- w++ 
> !O M V- PS+ PE+ Y PGP++ !t !5 X++++ R+ tv- b++ DI++ D++ 
> G++ e+++ h+ r-- y 
> ------END GEEK CODE BLOCK------
> 

Hi guys

In attachment is a file with "lsusb -v" output, please check it. if you
need something more feel free to tell me about it

Best regards Pawel


View attachment "lsusb" of type "text/plain" (29150 bytes)