Re: infos about device ZTE MF821D 2G,3G,4G/LTE usb-modem/networkcard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Thomas Schäfer <tschaefer@xxxxxxxxxxx> writes:
> Am Montag, 9. Juli 2012, 10:25:27 schrieben Sie:
>> Thomas Schäfer <tschaefer@xxxxxxxxxxx> writes:
>> > The modem works at /dev/USB2.
>> posted:
>> | diag  19d2:0326 MI00\6
>> | nema  19d2:0326 MI01\6
>> | at-   19d2:0326 MI02\6
>> | modem 19d2:0326 MI03\6
>> | ndis  19d2:0326 MI04\6
>> I am wondering a bit about the "modem" port here.  Is that a second AT
>> command interface?  According to your dmesg, it should be ttyUSB3 in
>> your setup:
> Yes, there are two interfaces (/dev/ttyUSB2 and /dev/ttyUSB3) which answers 
> "ok" to "at" and some other at-commands.
> The classic serial-ppp-internet-connection works at least with /dev/ttyUSB2
> I have to test /dev/ttyUSB3 if only "at" works or the whole ppp-stuff too.

Well, it doesn't matter for the drivers.  I just wanted to verify that
it is a serial interface and not something else.

>> Please prepare patches for the option and qmi_wwan (after verifying the
>> above assumption) drivers.  Yes, I could do so, or someone else could,
>> but you've already done most of the work so why not make sure you get
>> the proper credit? :-)
> I afraid if I create a working patch to a certain version, the version is very 
> obsolete. Or you or the maintainers have extra work, because of a lot of 
> beginner's mistakes.

Having been there, and still doing such mistakes, I can honestly say
that it's nothing to be afraid of.  That's just considered part of the
learning process.  The USB list is full of very kind and forgiving
people.  The worst that could possibly happen is that you have to redo
the patch.

> My knowledge about c-programming and usb-driver-layouts is at a very low 
> level.
> What for "proper credit"? 
> For adding some IDs?, while you and others wrote the whole driver, maintain 
> version for version, find bugs and improve the smallest details?
> That are your credits! 	 (seriously)

Well, if you think about it, you will realize that my contribution is
insignificant compared to e.g. the usbnet infrastructure I am leaning
on, and that contribution is still small compared to some other part of
the kernel, etc, etc.

Yes, I know that most of us don't do this for credits, but to make
something work. Proper accounting of the work being done still means
something to the community.

Anyway, it's an easy way to get to know the process. So that the next
time you get some new device with no driver, you might think "I can make
a driver for that".  And if you're like me, then you won't realize
you're wrong until it's too late :-)

> If you have time, please send me RFT-patches and the link to the version I 
> have to apply them. 
> This division of work was not wrong in past. 

OK, I can of course do that.

To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

B and H Foto and Electronics Corp.

[Linux Media]     [Video for Linux]     [Linux Input]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Free Online Dating]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]     [More Archives]

Add to Google Powered by Linux