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: Mon, 06 Jun 2011 17:21:27 +0400	[thread overview]
Message-ID: <4DECD457.60101@msgid.tls.msk.ru> (raw)
In-Reply-To: <BANLkTinAip5BswLBjxyJ1O_XPnUFq=FUjw@mail.gmail.com>

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@tls.msk.ru <mailto:mjt@tls.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------
> 


  parent reply	other threads:[~2011-06-06 13:21 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 [this message]
     [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=4DECD457.60101@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