public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Martin <oliver.martin@student.tuwien.ac.at>
To: linux-kernel@vger.kernel.org
Subject: Policy re. cellular USB modem mode switch
Date: Sat, 9 Aug 2008 04:45:30 +0200	[thread overview]
Message-ID: <20080809044530.193a077a@ors.home> (raw)

Hello,

trying to get my ZTE MF628 HSDPA modem to work left me wondering if
there is an established policy whether or not to include the "mode
switch" code most cellular USB modems need in the kernel or not.
Currently, the MF628 requires a userspace helper called usb_modeswitch
to be called [1] to change from mass storage mode to serial mode.
After, that it can be used with the usbserial driver or preferably,
after one adds the right vendor and product id, with the option driver.

The only other such device I know is the Huawei E220, which doesn't
require any userspace tools since 2.6.20. The usb_modeswitch website
lists quite a lot of devices as supported, do any other of them
*require* the use of this (or another) userspace tool? If so, is this
considered acceptable?

The main reason I'm asking this is to find out if I should try to put
the mode switch code in the kernel or not. In the meantime, I'll reply
to this message with a patch to add the vendor/product id of the MF628
to the option driver, which I guess is needed in any case.

Regards,
Oliver

[1] http://www.draisberghof.de/usb_modeswitch/
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=81

             reply	other threads:[~2008-08-09  2:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-09  2:45 Oliver Martin [this message]
2008-08-09  2:49 ` [PATCH] Add vendor/product id of ZTE MF628 to option Oliver Martin
2008-08-09  4:53   ` Greg KH
2008-08-09  4:38 ` Policy re. cellular USB modem mode switch Greg KH

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=20080809044530.193a077a@ors.home \
    --to=oliver.martin@student.tuwien.ac.at \
    --cc=linux-kernel@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