From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dan Williams <dcbw@redhat.com>
Date: Thu, 18 Mar 2010 23:54:11 +0000
Subject: Re: Functionality overlap between udev's modem-modeswitch and
Message-Id: <1268956451.28562.23.camel@localhost.localdomain>
List-Id: <linux-hotplug.vger.kernel.org>
References: <201003181748.41270.didier@raboud.com>
In-Reply-To: <201003181748.41270.didier@raboud.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

On Thu, 2010-03-18 at 18:16 +0100, Kay Sievers wrote:
> On Thu, Mar 18, 2010 at 17:48, Didier 'OdyX' Raboud <didier@raboud.com> wrote:
> > 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 :
> >
> >> # modem-modeswitch does not work with these devices, the fake CD-ROM needs to
> > be ejected
> >>
> >> # 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 :
> >
> >> # 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.

> 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