Re: TP-LINK HSUPA Modem MA180 2357:0201

2013-01-15 Thread Bjørn Mork
Thomas Schäfer tschae...@t-online.de writes:

 Here are all infos about this device. I think I catched the relevant data.

 Switching to modem/network-mode works with 

 eject /dev/sr0

 It works with option 
 /dev/ttyUSB2 has accepted at-commands

 and qmi_wwan (in testcase with interface 1 instead of 0)

 I was able get an IPv4- connection via qmi-interface.

 I was not able to get online via IPv6.

 qmi-version-infos are also inside the attachment.


 This is, what windows says about this device:

 Diagnostics USB\VID_2357PID_0201MI_00\637BC1CE00
 NMEAUSB\VID_2357PID_0201MI_01\637BC1CE01

 Modem   USB\VID_2357PID_0201MI_03\637BC1CE03
 Networkcard USB\VID_2357PID_0201MI_04\637BC1CE04


 mmc 
 USBSTOR\CDROMVEN_TP-LINKPROD_MMC_STORAGEREV_2.31\77ED6A6108630770103305650


 Labels at the housing:

 MA180
 FCC ID: T7MA180V2
 IC: 8853-MA180V1


 Windows-software at the stick is identical to 
 http://www.tp-link.com.de/Resources/software/MA180_V1_Easy_Setup_Assistant.zip
 (same md5)

Thanks a lot for the extra-ordinary complete and detailed report.  I've
just submitted the two patches this ends up as.  Given the amount of
work you put into collection all the info, you could have submitted
those patches yourself to save you some of the work :-)


Bjørn
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: TP-LINK HSUPA Modem MA180 2357:0201

2013-01-12 Thread Thomas Schäfer
Am Mittwoch, 9. Januar 2013, 22:24:14 schrieben Sie:

  No further work need to be done in the kernel.
 
 Are you able to provide the Windows .INF files from the device so we can
 determine what kernel drivers each interface of the device requires?
 Basically, instead of modeswitching the device, let the fake CD disk
 appear, tar+gzip the contents of the fake CD, and mail it to me so I can
 inspect it.

Diagnostics USB\VID_2357PID_0201MI_00\637BC1CE00
NMEAUSB\VID_2357PID_0201MI_01\637BC1CE01

Modem   USB\VID_2357PID_0201MI_03\637BC1CE03
Networkcard USB\VID_2357PID_0201MI_04\637BC1CE04


mmc 
USBSTOR\CDROMVEN_TP-LINKPROD_MMC_STORAGEREV_2.31\77ED6A6108630770103305650


 
 What specific model number is this device?  Is it the MA180?  Or is it
 the MA260?  What model number is printed on the device?  Does it have an
 FCC ID printed anywhere on it?


MA180

FCC ID: T7MA180V2
IC: 8853-MA180V1

The examination at linux I will start later this day. 

Regards,

Thomas


--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


TP-LINK HSUPA Modem MA180 2357:0201

2013-01-12 Thread Thomas Schäfer
Here are all infos about this device. I think I catched the relevant data.

Switching to modem/network-mode works with 

eject /dev/sr0

It works with option 
/dev/ttyUSB2 has accepted at-commands

and qmi_wwan (in testcase with interface 1 instead of 0)

I was able get an IPv4- connection via qmi-interface.

I was not able to get online via IPv6.

qmi-version-infos are also inside the attachment.


This is, what windows says about this device:

Diagnostics USB\VID_2357PID_0201MI_00\637BC1CE00
NMEAUSB\VID_2357PID_0201MI_01\637BC1CE01

Modem   USB\VID_2357PID_0201MI_03\637BC1CE03
Networkcard USB\VID_2357PID_0201MI_04\637BC1CE04


mmc 
USBSTOR\CDROMVEN_TP-LINKPROD_MMC_STORAGEREV_2.31\77ED6A6108630770103305650


Labels at the housing:

MA180
FCC ID: T7MA180V2
IC: 8853-MA180V1


Windows-software at the stick is identical to 
http://www.tp-link.com.de/Resources/software/MA180_V1_Easy_Setup_Assistant.zip
(same md5)


Thomas




--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


tp-link-ma180.tgz
Description: application/compressed-tar