Skip to contentSkip to conversation

Functionality overlap between udev's modem-modeswitch and usb-modeswitch about 19d2:2000

DISCUSSION Didier 'OdyX' Raboud 3 participants 3 messages Mar 18, 2010

lore
Share & tools
lore
#0 lore raw

Hi udev upstreams !

(please keep me and the Debian bug CC'ed).

I am the Debian maintainer for usb-modeswitch and I got a user reporting that his 3G dongle was not "switched" anymore [0]. After some investigation, I strongly suspect that udev's modem-modeswitch and usb-modeswitch have a conflicting functionality overlap.

From /lib/udev/rules.d/61-mobile-action.rules :

Quoted 1 line
# modem-modeswitch does not work with these devices, the fake CD-ROM needs to 

be ejected

Quoted 3 lines

# ZTE MF6xx
ACTION=="add", ENV{ID_CDROM}=="1", ENV{ID_VENDOR_ID}=="19d2",

ENV{ID_MODEL_ID}=="2000", RUN+="/usr/bin/eject %k"

From /lib/udev/rules.d/40-usb_modeswitch.rules :

Quoted 2 lines

# ZTE devices
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="2000", RUN+="usb_modeswitch

'%b/%k'"

It seems (to me) that those lines should be removed from udev (as usb-modeswitch provides a generic switching facility for more than "just" 19d2:2000.

What is your opinion thereabout ?

Thanks in advance and best regards,

OdyX

[0] http://bugs.debian.org/574270

Signature · 3 lines
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
[email protected]
#1 lore raw

Re: Functionality overlap between udev's modem-modeswitch and

Quoted 20 lines · Didier 'OdyX' Raboud

Hi udev upstreams !

(please keep me and the Debian bug CC'ed).

I am the Debian maintainer for usb-modeswitch and I got a user reporting that his 3G dongle was not "switched" anymore [0]. After some investigation, I strongly suspect that udev's modem-modeswitch and usb-modeswitch have a conflicting functionality overlap.

From /lib/udev/rules.d/61-mobile-action.rules :

Quoted 1 line
# modem-modeswitch does not work with these devices, the fake CD-ROM needs to

be ejected

Quoted 3 lines

# ZTE MF6xx
ACTION="add", ENV{ID_CDROM}="1", ENV{ID_VENDOR_ID}="19d2",

ENV{ID_MODEL_ID}="2000", RUN+="/usr/bin/eject %k"

From /lib/udev/rules.d/40-usb_modeswitch.rules :

Quoted 8 lines
Quoted 2 lines

# ZTE devices
ATTRS{idVendor}="19d2", ATTRS{idProduct}="2000", RUN+="usb_modeswitch

'%b/%k'"

It seems (to me) that those lines should be removed from udev (as usb-modeswitch provides a generic switching facility for more than "just" 19d2:2000.

What is your opinion thereabout ?

If Dan has no objections, we are ready to delete modem-modeswitch from the udev tree.

Kay

#2 lore raw

Re: Functionality overlap between udev's modem-modeswitch and

In reply to Didier 'OdyX' Raboud
Quoted 21 lines · Kay Sievers
Quoted 20 lines · Didier 'OdyX' Raboud

Hi udev upstreams !

(please keep me and the Debian bug CC'ed).

I am the Debian maintainer for usb-modeswitch and I got a user reporting that his 3G dongle was not "switched" anymore [0]. After some investigation, I strongly suspect that udev's modem-modeswitch and usb-modeswitch have a conflicting functionality overlap.

From /lib/udev/rules.d/61-mobile-action.rules :

Quoted 1 line
# modem-modeswitch does not work with these devices, the fake CD-ROM needs to

be ejected

Quoted 3 lines

# ZTE MF6xx
ACTION="add", ENV{ID_CDROM}="1", ENV{ID_VENDOR_ID}="19d2",

ENV{ID_MODEL_ID}="2000", RUN+="/usr/bin/eject %k"

From /lib/udev/rules.d/40-usb_modeswitch.rules :

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines

# ZTE devices
ATTRS{idVendor}="19d2", ATTRS{idProduct}="2000", RUN+="usb_modeswitch

'%b/%k'"

It seems (to me) that those lines should be removed from udev (as usb-modeswitch provides a generic switching facility for more than "just" 19d2:2000.

What is your opinion thereabout ?

People seem to have a hard time understanding that "Mobile Action" and "Option" are not the companies as ZTE and Huawei, unfortunately. I don't really understand that.

However, some of that confusion comes from having duplicate mode switching tools.

Quoted 2 lines

If Dan has no objections, we are ready to delete modem-modeswitch from the udev tree.

usb_modeswitch still doesn't do the Mobile Action cable stuff. So I'll spin modem-modeswitch into a standalone tool that *only* switches the mobile action cables. Then we can remove the confusion and just use usb_modeswitch.

Dan