1:38 a.m.
Based on the latest usb_modeswitch rules, some 3G dongles require
to modify the ofono rules to be supported correctly (tests done in India)
Philippe Nunes (3):
udev: use ttyUSB3 for ZTE K3570 modem port.
udev: add support for Olive HSDPA modem
udev: Use ttyUSB4 for Huawei E367 Pcui port
plugins/ofono.rules | 17 ++++++++++-------
1 files changed, 10 insertions(+), 7 deletions(-)
1:38 a.m.
New subject: [PATCH 1/3] udev: use ttyUSB3 for ZTE K3570 modem port.
---
plugins/ofono.rules | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/plugins/ofono.rules b/plugins/ofono.rules
index 4143e17..82232d9 100644
--- a/plugins/ofono.rules
+++ b/plugins/ofono.rules
@@ -35,7 +35,7 @@ ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0121",
ENV{ID_USB_INTERFACE_NUM}=="0
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0124",
ENV{ID_USB_INTERFACE_NUM}=="04", ENV{OFONO_ZTE_TYPE}="modem"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0124",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_ZTE_TYPE}="aux"
-ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="02", ENV{OFONO_ZTE_TYPE}="modem"
+ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="03", ENV{OFONO_ZTE_TYPE}="modem"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_ZTE_TYPE}="aux"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="2003",
ENV{ID_USB_INTERFACE_NUM}=="03", ENV{OFONO_ZTE_TYPE}="modem"
--
1.7.1
1:38 a.m.
New subject: [PATCH 2/3] udev: add support for Olive HSDPA modem
---
plugins/ofono.rules | 13 ++++++++-----
1 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/plugins/ofono.rules b/plugins/ofono.rules
index 82232d9..a361e70 100644
--- a/plugins/ofono.rules
+++ b/plugins/ofono.rules
@@ -376,9 +376,12 @@ ATTRS{idVendor}=="1c9e",
ATTRS{idProduct}=="9800", ENV{ID_USB_INTERFACE_NUM}=="0
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e00",
ENV{ID_USB_INTERFACE_NUM}=="00", ENV{OFONO_SPEEDUP_TYPE}="modem"
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e00",
ENV{ID_USB_INTERFACE_NUM}=="03", ENV{OFONO_SPEEDUP_TYPE}="aux"
-# SpeedUp 8000
-ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="03", ENV{OFONO_SPEEDUP_TYPE}="modem"
-ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_SPEEDUP_TYPE}="aux"
+# SpeedUp
+ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1005",
ENV{ID_USB_INTERFACE_NUM}=="03", ENV{OFONO_SPEEDUP_TYPE}="modem"
+ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1005",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_SPEEDUP_TYPE}="aux"
+
+ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_SPEEDUP_TYPE}="modem"
+ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="03", ENV{OFONO_SPEEDUP_TYPE}="aux"
# Olive
ATTRS{idVendor}=="201e", ATTRS{idProduct}=="2009",
ENV{ID_USB_INTERFACE_NUM}=="00", ENV{OFONO_HUAWEI_TYPE}="Modem"
@@ -434,8 +437,8 @@ ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9800",
ENV{OFONO_DRIVER}="speedup"
ATTRS{idVendor}=="1c9e", ATTRS{serial}=="1234567890ABCDEF",
ENV{ID_SERIAL_SHORT}=""
-# SpeedUp 8000
-ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{OFONO_DRIVER}="speedup"
+# SpeedUp
+ATTRS{idVendor}=="2020", ENV{OFONO_DRIVER}="speedup"
ATTRS{idVendor}=="2020", ATTRS{serial}=="1234567890ABCDEF",
ENV{ID_SERIAL_SHORT}=""
--
1.7.1
10:49 a.m.
New subject: [PATCH 2/3] udev: add support for Olive HSDPA modem
-----Original Message-----
From: ofono-bounces(a)ofono.org [mailto:ofono-bounces@ofono.org] On Behalf
Of Philippe Nunes
Sent: Thursday, August 11, 2011 11:38 PM
To: ofono(a)ofono.org
Subject: [PATCH 2/3] udev: add support for Olive HSDPA modem
---
plugins/ofono.rules | 13 ++++++++-----
1 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/plugins/ofono.rules b/plugins/ofono.rules
index 82232d9..a361e70 100644
--- a/plugins/ofono.rules
+++ b/plugins/ofono.rules
@@ -376,9 +376,12 @@ ATTRS{idVendor}=="1c9e",
ATTRS{idProduct}=="9800", ENV{ID_USB_INTERFACE_NUM}=="0
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e00",
ENV{ID_USB_INTERFACE_NUM}=="00",
ENV{OFONO_SPEEDUP_TYPE}="modem"
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e00",
ENV{ID_USB_INTERFACE_NUM}=="03", ENV{OFONO_SPEEDUP_TYPE}="aux"
-# SpeedUp 8000
-ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="03",
ENV{OFONO_SPEEDUP_TYPE}="modem"
-ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_SPEEDUP_TYPE}="aux"
+# SpeedUp
+ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1005",
ENV{ID_USB_INTERFACE_NUM}=="03",
ENV{OFONO_SPEEDUP_TYPE}="modem"
+ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1005",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_SPEEDUP_TYPE}="aux"
+
+ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="01",
ENV{OFONO_SPEEDUP_TYPE}="modem"
+ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{ID_USB_INTERFACE_NUM}=="03", ENV{OFONO_SPEEDUP_TYPE}="aux"
Dear Philippe,
The modem port shall be 03 and aux port shall be 01 for 2020: 1008 (SU8000) modem.
# Olive
ATTRS{idVendor}=="201e", ATTRS{idProduct}=="2009",
ENV{ID_USB_INTERFACE_NUM}=="00",
ENV{OFONO_HUAWEI_TYPE}="Modem"
@@ -434,8 +437,8 @@ ATTRS{idVendor}=="1c9e",
ATTRS{idProduct}=="9800",
ENV{OFONO_DRIVER}="speedup"
ATTRS{idVendor}=="1c9e", ATTRS{serial}=="1234567890ABCDEF",
ENV{ID_SERIAL_SHORT}=""
-# SpeedUp 8000
-ATTRS{idVendor}=="2020", ATTRS{idProduct}=="1008",
ENV{OFONO_DRIVER}="speedup"
+# SpeedUp
+ATTRS{idVendor}=="2020", ENV{OFONO_DRIVER}="speedup"
ATTRS{idVendor}=="2020", ATTRS{serial}=="1234567890ABCDEF",
ENV{ID_SERIAL_SHORT}=""
--
1.7.1
_______________________________________________
ofono mailing list
ofono(a)ofono.org
http://lists.ofono.org/listinfo/ofono
1:38 a.m.
New subject: [PATCH 3/3] udev: Use ttyUSB4 for Huawei E367 Pcui port
---
plugins/ofono.rules | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/plugins/ofono.rules b/plugins/ofono.rules
index a361e70..5e59425 100644
--- a/plugins/ofono.rules
+++ b/plugins/ofono.rules
@@ -363,7 +363,7 @@ ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1486",
ENV{ID_USB_INTERFACE_NUM}=="0
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1486",
ENV{ID_USB_INTERFACE_NUM}=="02", ENV{OFONO_HUAWEI_TYPE}="Pcui"
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506",
ENV{ID_USB_INTERFACE_NUM}=="00", ENV{OFONO_HUAWEI_TYPE}="Modem"
-ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_HUAWEI_TYPE}="Pcui"
+ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1506",
ENV{ID_USB_INTERFACE_NUM}=="04", ENV{OFONO_HUAWEI_TYPE}="Pcui"
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1c05",
ENV{ID_USB_INTERFACE_NUM}=="00", ENV{OFONO_HUAWEI_TYPE}="Modem"
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1c05",
ENV{ID_USB_INTERFACE_NUM}=="02", ENV{OFONO_HUAWEI_TYPE}="Pcui"
--
1.7.1
2:21 a.m.
Hi Philippe,
Based on the latest usb_modeswitch rules, some 3G dongles require
to modify the ofono rules to be supported correctly (tests done in India)
Philippe Nunes (3):
udev: use ttyUSB3 for ZTE K3570 modem port.
udev: add support for Olive HSDPA modem
udev: Use ttyUSB4 for Huawei E367 Pcui port
plugins/ofono.rules | 17 ++++++++++-------
1 files changed, 10 insertions(+), 7 deletions(-)
I think you are way too late with these changes. We are not using
plugins/udev.c for Huawei and ZTE device detection anymore. I fixed this
all up and plugins/udevng.c should do proper automatic detection.
Please check if this works properly for you or if you have problems.
Regards
Marcel
1:26 a.m.
On 08/11/2011 06:21 PM, Marcel Holtmann wrote:
Hi Philippe,
> Based on the latest usb_modeswitch rules, some 3G dongles require
> to modify the ofono rules to be supported correctly (tests done in India)
>
>
> Philippe Nunes (3):
> udev: use ttyUSB3 for ZTE K3570 modem port.
> udev: add support for Olive HSDPA modem
> udev: Use ttyUSB4 for Huawei E367 Pcui port
>
> plugins/ofono.rules | 17 ++++++++++-------
> 1 files changed, 10 insertions(+), 7 deletions(-)
I think you are way too late with these changes. We are not using
plugins/udev.c for Huawei and ZTE device detection anymore. I fixed this
all up and plugins/udevng.c should do proper automatic detection.
Please check if this works properly for you or if you have problems.
Hi Marcel,
I just experienced a case where the automatic detection brings a
difference with the previous implementation.
Using the dongle ZTE MF190 (DefaultProduct= 0x0149 TargetProduct=
0x0124), udevng.c is assigning the modem port to ttyUSB3 whereas ttyUSB4
was assigned with the previous udev.c based on the previous ofono.rules.
In practice, the port com ttyUSB3 is not responsive (I checked also with
minicom) so we can't manage to connect a data call (see ofono logs in
attachment). Using the previous combination udev.c + ofono.rules, if
the modem port assigned to ttyUSB4 is responsive, we are however facing
with an other issue:
ofonod[23908]: plugins/zte.c:zte_post_online() 0x9e2a470
ofonod[23908]: Aux: > AT+CREG=?\r
ofonod[23908]: Aux: < \r\nOK\r\n
ofonod[23908]: Unable to initialize Network Registration
ofonod[23908]: src/network.c:netreg_remove() atom: 0x9e29cf0
So, we can't go ahead for the data call since the network is not
registered. But this is an other issue we would need to fix I guess
specifically for this dongle.
Here, I just wanted to raise a potential issue regarding the modem port
com assignment for ZTE dongles:
Indeed, according the previous ofono.rules, we were assigning ttyUSB4 as
modem port for 2 product Ids:
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0121",
ENV{ID_USB_INTERFACE_NUM}=="04", ENV{OFONO_ZTE_TYPE}="modem"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0121",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_ZTE_TYPE}="aux"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0124",
ENV{ID_USB_INTERFACE_NUM}=="04", ENV{OFONO_ZTE_TYPE}="modem"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0124",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_ZTE_TYPE}="aux"
but looking to udevng.c and particularly the function 'setup_zte', the
modem port can't be assigned anymore to ttyUSB4.
static gboolean setup_zte(struct modem_info *modem)
{
...
if (g_strcmp0(info->number, "00") == 0)
qcdm = info->devnode;
else if (g_strcmp0(info->number, "01") == 0)
aux = info->devnode;
else if (g_strcmp0(info->number, "02") == 0)
mdm = info->devnode;
else if (g_strcmp0(info->number, "03") == 0)
mdm = info->devnode;
}
}
So, I wonder if the condition:
else if (g_strcmp0(info->number, "04") == 0)
is voluntarily missing or not.
Please, could you clarify?
Thanks.
Regards,
Philippe.
2:13 a.m.
Hi Phillipe,
>> Based on the latest usb_modeswitch rules, some 3G dongles
require
>> to modify the ofono rules to be supported correctly (tests done in India)
>>
>>
>> Philippe Nunes (3):
>> udev: use ttyUSB3 for ZTE K3570 modem port.
>> udev: add support for Olive HSDPA modem
>> udev: Use ttyUSB4 for Huawei E367 Pcui port
>>
>> plugins/ofono.rules | 17 ++++++++++-------
>> 1 files changed, 10 insertions(+), 7 deletions(-)
>
> I think you are way too late with these changes. We are not using
> plugins/udev.c for Huawei and ZTE device detection anymore. I fixed this
> all up and plugins/udevng.c should do proper automatic detection.
>
> Please check if this works properly for you or if you have problems.
>
Hi Marcel,
I just experienced a case where the automatic detection brings a
difference with the previous implementation.
Using the dongle ZTE MF190 (DefaultProduct= 0x0149 TargetProduct=
0x0124), udevng.c is assigning the modem port to ttyUSB3 whereas ttyUSB4
was assigned with the previous udev.c based on the previous ofono.rules.
In practice, the port com ttyUSB3 is not responsive (I checked also with
minicom) so we can't manage to connect a data call (see ofono logs in
attachment). Using the previous combination udev.c + ofono.rules, if
the modem port assigned to ttyUSB4 is responsive, we are however facing
with an other issue:
ofonod[23908]: plugins/zte.c:zte_post_online() 0x9e2a470
ofonod[23908]: Aux: > AT+CREG=?\r
ofonod[23908]: Aux: < \r\nOK\r\n
ofonod[23908]: Unable to initialize Network Registration
ofonod[23908]: src/network.c:netreg_remove() atom: 0x9e29cf0
So, we can't go ahead for the data call since the network is not
registered. But this is an other issue we would need to fix I guess
specifically for this dongle.
Here, I just wanted to raise a potential issue regarding the modem port
com assignment for ZTE dongles:
Indeed, according the previous ofono.rules, we were assigning ttyUSB4 as
modem port for 2 product Ids:
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0121",
ENV{ID_USB_INTERFACE_NUM}=="04", ENV{OFONO_ZTE_TYPE}="modem"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0121",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_ZTE_TYPE}="aux"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0124",
ENV{ID_USB_INTERFACE_NUM}=="04", ENV{OFONO_ZTE_TYPE}="modem"
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0124",
ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_ZTE_TYPE}="aux"
but looking to udevng.c and particularly the function 'setup_zte', the
modem port can't be assigned anymore to ttyUSB4.
static gboolean setup_zte(struct modem_info *modem)
{
...
if (g_strcmp0(info->number, "00") == 0)
qcdm = info->devnode;
else if (g_strcmp0(info->number, "01") == 0)
aux = info->devnode;
else if (g_strcmp0(info->number, "02") == 0)
mdm = info->devnode;
else if (g_strcmp0(info->number, "03") == 0)
mdm = info->devnode;
}
}
So, I wonder if the condition:
else if (g_strcmp0(info->number, "04") == 0)
is voluntarily missing or not.
it might be missing. What does usb-devices say and how many TTY is this
one actually creating. If it creates indeed 5 TTY and the fourth TTY is
on interface number 04, then yes this should be added.
The general rule for ZTE is that the modem interface is suppose to be on
the last interface. Not sure if this is always true, but with all my
devices it was. And we could still overwrite this with a udev rule if we
have to.
Regards
Marcel
8:34 p.m.
On 08/23/2011 06:13 PM, Marcel Holtmann wrote:
Hi Phillipe,
>>> Based on the latest usb_modeswitch rules, some 3G dongles require
>>> to modify the ofono rules to be supported correctly (tests done in India)
>>>
>>>
>>> Philippe Nunes (3):
>>> udev: use ttyUSB3 for ZTE K3570 modem port.
>>> udev: add support for Olive HSDPA modem
>>> udev: Use ttyUSB4 for Huawei E367 Pcui port
>>>
>>> plugins/ofono.rules | 17 ++++++++++-------
>>> 1 files changed, 10 insertions(+), 7 deletions(-)
>>
>> I think you are way too late with these changes. We are not using
>> plugins/udev.c for Huawei and ZTE device detection anymore. I fixed this
>> all up and plugins/udevng.c should do proper automatic detection.
>>
>> Please check if this works properly for you or if you have problems.
>>
>
>
> Hi Marcel,
>
> I just experienced a case where the automatic detection brings a
> difference with the previous implementation.
>
> Using the dongle ZTE MF190 (DefaultProduct= 0x0149 TargetProduct=
> 0x0124), udevng.c is assigning the modem port to ttyUSB3 whereas ttyUSB4
> was assigned with the previous udev.c based on the previous ofono.rules.
>
> In practice, the port com ttyUSB3 is not responsive (I checked also with
> minicom) so we can't manage to connect a data call (see ofono logs in
> attachment). Using the previous combination udev.c + ofono.rules, if
> the modem port assigned to ttyUSB4 is responsive, we are however facing
> with an other issue:
>
> ofonod[23908]: plugins/zte.c:zte_post_online() 0x9e2a470
> ofonod[23908]: Aux:> AT+CREG=?\r
> ofonod[23908]: Aux:< \r\nOK\r\n
> ofonod[23908]: Unable to initialize Network Registration
> ofonod[23908]: src/network.c:netreg_remove() atom: 0x9e29cf0
>
>
> So, we can't go ahead for the data call since the network is not
> registered. But this is an other issue we would need to fix I guess
> specifically for this dongle.
>
> Here, I just wanted to raise a potential issue regarding the modem port
> com assignment for ZTE dongles:
>
> Indeed, according the previous ofono.rules, we were assigning ttyUSB4 as
> modem port for 2 product Ids:
>
> ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0121",
> ENV{ID_USB_INTERFACE_NUM}=="04", ENV{OFONO_ZTE_TYPE}="modem"
> ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0121",
> ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_ZTE_TYPE}="aux"
>
> ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0124",
> ENV{ID_USB_INTERFACE_NUM}=="04", ENV{OFONO_ZTE_TYPE}="modem"
> ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0124",
> ENV{ID_USB_INTERFACE_NUM}=="01", ENV{OFONO_ZTE_TYPE}="aux"
>
> but looking to udevng.c and particularly the function 'setup_zte', the
> modem port can't be assigned anymore to ttyUSB4.
>
> static gboolean setup_zte(struct modem_info *modem)
> {
> ...
>
> if (g_strcmp0(info->number, "00") == 0)
> qcdm = info->devnode;
> else if (g_strcmp0(info->number, "01") == 0)
> aux = info->devnode;
> else if (g_strcmp0(info->number, "02") == 0)
> mdm = info->devnode;
> else if (g_strcmp0(info->number, "03") == 0)
> mdm = info->devnode;
> }
> }
>
> So, I wonder if the condition:
>
> else if (g_strcmp0(info->number, "04") == 0)
>
> is voluntarily missing or not.
it might be missing. What does usb-devices say and how many TTY is this
one actually creating. If it creates indeed 5 TTY and the fourth TTY is
on interface number 04, then yes this should be added.
The general rule for ZTE is that the modem interface is suppose to be on
the last interface. Not sure if this is always true, but with all my
devices it was. And we could still overwrite this with a udev rule if we
have to.
Regards
Marcel
Hi Marcel,
Actually, with this dongle, we have 6 TTY (usb0 -> usb5) and usb-devices
gives:
T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 32 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=19d2 ProdID=0124 Rev=00.00
S: Manufacturer=ZTE,Incorporated
S: Product=ZTE WCDMA Technologies MSM
S: SerialNumber=P671A2TMED010000
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 6 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
Now, ttyUSB5 is not responsive. So, for this particular dongle, the
modem interface won't be on the last interface. Anyway, as I'm just
looking to add the condition related to the interface number 04, it
doesn't really matter.
Regards,
Philippe.
2:21 a.m.
Hi Philippe,
Actually, with this dongle, we have 6 TTY (usb0 -> usb5) and
usb-devices
gives:
T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 32 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=19d2 ProdID=0124 Rev=00.00
S: Manufacturer=ZTE,Incorporated
S: Product=ZTE WCDMA Technologies MSM
S: SerialNumber=P671A2TMED010000
C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 6 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
Now, ttyUSB5 is not responsive. So, for this particular dongle, the
modem interface won't be on the last interface. Anyway, as I'm just
looking to add the condition related to the interface number 04, it
doesn't really matter.
so on which interfaces do we actually have the modem and the aux channel
now.
And more important now, do we use the right usb_modeswitch magic to
switch it into this mode. Or is Windows using something different?
Regards
Marcel
11:48 p.m.
On 08/24/2011 06:21 PM, Marcel Holtmann wrote:
Hi Philippe,
> Actually, with this dongle, we have 6 TTY (usb0 -> usb5) and usb-devices
> gives:
>
> T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 32 Spd=480 MxCh= 0
> D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
> P: Vendor=19d2 ProdID=0124 Rev=00.00
> S: Manufacturer=ZTE,Incorporated
> S: Product=ZTE WCDMA Technologies MSM
> S: SerialNumber=P671A2TMED010000
> C: #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
> I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#= 5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
> I: If#= 6 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
>
> Now, ttyUSB5 is not responsive. So, for this particular dongle, the
> modem interface won't be on the last interface. Anyway, as I'm just
> looking to add the condition related to the interface number 04, it
> doesn't really matter.
so on which interfaces do we actually have the modem and the aux channel
now.
Actually, with current udevng.c, aux channel is on ttyUSB1 and modem is
on ttyUSB3. But in practice, modem should be on ttyUSB4.
And more important now, do we use the right usb_modeswitch magic to
switch it into this mode.
My configuration:
usb modeswitch Version 1.1.8, 2011/06/19
usb modeswitch data package 2011/07/14
Or is Windows using something different?
Windows Device Manager gives the following results:
Vendor Id: 19d2 / Product Id: 0124 (same as after usb_modeswitch)
ZTE Diagnostic port - 00
ZTE AT port - 01
ZTE ATExt2 port - 02
ZTE USB SmartCard Reader - 03
ZTE Proprietary USB Modem - 04
ZTE Mobile broadband Network manager - 05
So, it confirms that the modem port com is on ttyUSB4.
For ZTE, the proposed change (add the condition related to the interface
number 04) seems relevant.
Now, I found an other mismatch with Speedup dongles:
In practice, enabling the dongle speedup SU-7300 fails actually in timeout.
Looking to the oFono traces, we have:
...
ofonod[32238]: plugins/udevng.c:setup_speedup()
/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1
ofonod[32238]: plugins/udevng.c:setup_speedup() /dev/ttyUSB0 255/255/255
00 (null)
ofonod[32238]: plugins/udevng.c:setup_speedup() /dev/ttyUSB1 255/255/255
01 (null)
ofonod[32238]: plugins/udevng.c:setup_speedup() /dev/ttyUSB2 255/255/255
02 (null)
ofonod[32238]: plugins/udevng.c:setup_speedup() /dev/ttyUSB3 255/255/255
03 (null)
ofonod[32238]: plugins/udevng.c:setup_speedup() /dev/ttyUSB4 255/255/255
04 (null)
ofonod[32238]: plugins/udevng.c:setup_speedup() aux=/dev/ttyUSB1
modem=/dev/ttyUSB3
...
ofonod[32238]: plugins/speedupcdma.c:open_device() Modem /dev/ttyUSB3
ofonod[32238]: src/modem.c:get_modem_property() modem 0x9a0bc00 property Aux
ofonod[32238]: plugins/speedupcdma.c:open_device() Aux /dev/ttyUSB1
ofonod[32238]: Modem: > ATE0 &C0 +CMEE=1\r
ofonod[32238]: Aux: > ATE0 &C0 +CMEE=1\r
ofonod[32238]: Modem: < ATE0 &C0 +CMEE=1\r\r\nOK\r\n
ofonod[32238]: src/modem.c:set_powered_timeout() modem: 0x9a0bc00
Aux channel is not responsive.
As you can see, aux channel is now set to ttyUSB1 whereas it was set
previously to ttyUSB3 (as stated by the rules below).
# SpeedUp 7300
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e00",
ENV{ID_USB_INTERFACE_NUM}=="00", ENV{OFONO_SPEEDUP_TYPE}="modem"
ATTRS{idVendor}=="1c9e", ATTRS{idProduct}=="9e00",
ENV{ID_USB_INTERFACE_NUM}=="03", ENV{OFONO_SPEEDUP_TYPE}="aux"
Looking to the previous ofono rules related to speedup dongles, aux
channel was always assigned to the last interface. Now, with udevng.c,
aux channel is always assigned to ttyUSB1 and modem is set on the last
interface.
So, currently, aux channel and modem channel are switched.
But in practice, this seems wrong.
I tried indeed with a Speedup 9800 and I could notice that the network
registration unsolicited result codes (+CREG, +CGREG) were received on
the modem channel instead of the aux channel. This issue is raised
already by the bug #20553 (Meego)
Now, if the aux channel is set properly on the last interface, the
remaining issue is that the modem channel can't be always assigned on
ttyUSB1.
At least for speedup 7300 (and generally for speedup cdma dongles ?),
modem channel should be assigned to ttyUSB0.
So, I propose the following change in udevng.c:
@@ -311,12 +311,17 @@ static gboolean setup_speedup(struct modem_info
*modem)
if (aux != NULL)
break;
} else if (g_strcmp0(info->interface, "255/255/255") == 0) {
- if (g_strcmp0(info->number, "01") == 0)
- aux = info->devnode;
- else if (g_strcmp0(info->number, "02") == 0)
+ if (g_strcmp0(info->number, "00") == 0 &&
+ g_strcmp0(modem->driver,
+ "speedupcdma") == 0)
mdm = info->devnode;
- else if (g_strcmp0(info->number, "03") == 0)
+ else if (g_strcmp0(info->number, "01") == 0 &&
+ mdm == NULL)
mdm = info->devnode;
+ else if (g_strcmp0(info->number, "02") == 0)
+ aux = info->devnode;
+ else if (g_strcmp0(info->number, "03") == 0)
+ aux = info->devnode;
}
}
Please, let me know if I can go ahead with a proper patch.
Thanks,
Regards,
Philippe.
4042
days inactive
4056
days old
10 comments
3 participants
participants (3)
-
Deng, Ying An -
Marcel Holtmann -
Philippe Nunes