RE: option.ko: ZTE MF636 support

[Nils Radtke <lkml@Think-Future.de>]

  Hi Peter,

>> Similar symptoms are the long delay on opening of devices 0 and 2.
>> /dev/ttyUSB0: status port
>> /dev/ttyUSB2: modem port (not working)
>Does "echo > /dev/ttyUSB0" return immediately, and "echo > /dev/ttyUSB2"
>take around 15 seconds to return?
Indeed, that's exactly what's happening.

>> What has been your solution to get the ZTE working?
>I've blacklisted devices 0, 1 and 2 using the attached patch, taken
>against 2.6.34-rc6.  It should be quite straightforward to modify this
>for your device.
Ah. It seems that there's been quite some change in the code base of the
option driver. Using .33.3 here. No such thing as "blacklisting".

>Without the patch, I'm able to use wvdial against ttyUSB3 to dial up,
>but the device is unresponsive to anything apart from a PPP LCP
>disconnect.
For the olicard100 it's been port 2, dialling, pppd starting up, but lcp 
cfg req timeouts. At least with the olicard100 there's been no real dialup.
Conn endpoint has never been talking to the device..

Thanks alot for your hint. Previously I intended to wait for the .34 to
come out, but regarding the promising changes in option.c I will reconѕider this.
What are your overall xp with .34 so far? rc-7 is out, quite a rc count.. Maybe
the .34 is also levelling out these days.. :)

Cheers,

Nils