From: Dan Williams <dcbw@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: modem mode switching
Date: Thu, 13 Aug 2009 17:09:28 +0000 [thread overview]
Message-ID: <1250183368.5896.26.camel@localhost.localdomain> (raw)
In-Reply-To: <4A8433DA.3040003@pardus.org.tr>
On Thu, 2009-08-13 at 19:57 +0300, Ozan Çağlayan wrote:
> Dan Williams wrote:
> > On Thu, 2009-08-13 at 17:59 +0200, Kay Sievers wrote:
> >
> >> On Thu, Aug 13, 2009 at 17:40, Ozan Çağlayan<ozan@pardus.org.tr> wrote:
> >>
> >>> I wonder why there are two different userspace utilities for mode
> >>> switching on HSDPA modems. modem-modeswitch is shipped with udev,
> >>> usb_modeswitch is another project which is maintained as well.
> >>>
> >>> Do they diverge in some point? If not, are there any plan to merge them
> >>> together? I'm not sure but relevant kernel drivers for those modems
> >>> seems to also have some sort of mode switching. When I plug my Huawei
> >>> device which isn't listed in neither udev rules for the userspace, it
> >>> first gets probed as an unknown 0xffffffff device and then it gets
> >>> reconnected and probbed as a serial modem. If kernel-space is able to
> >>> handle those kind of quirks, why the user space mode switching tools exist?
> >>>
> >> Dan should know.
> >>
> >
> > Various reasons, none of which I care about any more, since the tool
> > works and as long as there's *something* that does the job, that's
> > great.
> >
> > We could move the mobile action code into a separate binary since it
> > doesn't look like it would be that easy to fit into usb_modeswitch's
> > current architecture.
> >
>
> So what I understand from here is that the tools are not mutually
> exclusive in terms of functionality. Is there a thing like "mode
> switching on X can only be done with usb_modeswitch/modem-modeswitch" ?
>
> I'm trying to understand if I have to package and ship usb_modeswitch
> tool along with the in-udev modem-modeswitch for making various devices
> detected out-of-the-box.
Now I remember why I disliked usb_modeswitch: it's architecture doesn't
allow out-of-the-box operation. You apparently have to uncomment your
device in the config file, or tell it exactly what you want it to do,
which pretty much duplicates what's in the config file.
What usb_modeswitch *should* be doing here is to just run, find all
devices that match something in the config file, and modeswitch them
automatically.
Ideally, we just fix usb_modeswitch to not be so unhelpful for
packagers/distributions, because it's an active project.
Dan
prev parent reply other threads:[~2009-08-13 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 15:40 modem mode switching Ozan Çağlayan
2009-08-13 15:59 ` Kay Sievers
2009-08-13 16:52 ` Dan Williams
2009-08-13 16:57 ` Ozan Çağlayan
2009-08-13 17:09 ` Dan Williams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1250183368.5896.26.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).