[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1453755751.3994.2.camel@devoid-pointer.net>
Date: Mon, 25 Jan 2016 22:02:31 +0100
From: Michal Malý <madcatxster@...oid-pointer.net>
To: Jiri Kosina <jikos@...nel.org>
Cc: Bjørn Mork <bjorn@...k.no>,
gregkh@...uxfoundation.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, dmitry.torokhov@...il.com,
elias.vds@...il.com, edwin@...ds.nl, simon@...gewell.org
Subject: Re: [PATCH 0/2] Add a skeleton module to perform a basic
initialization on certain USB devices
On Mon, 2016-01-25 at 15:17 +0100, Jiri Kosina wrote:
> On Sat, 23 Jan 2016, Michal Malý wrote:
>
> > I briefly considered leaving the switch up to the userspace and
> handling the
> > device in the kernel only once it's been switched. I am however
> uncertain how
> > to advertise this to the users. Writing a tiny app that would
> currently handle
> > just one device seems like an overkill, abusing usb_modeswitch
> seems counter-
> > intuitive as it's purpose is to handle various USB modems.
>
> Well, originally usb_modeswitch (beware, it's called "modeswitch",
> not
> "modemswitch" :) ) was purely for handling ZeroCD on USB 3G modems,
> and
> it's currently still by far the most common case, but there are
> other
> devices being handled by that package now; I for example recall some
> HP printers needing a magic USB command to be sent to it before they
> would
> start printing, and usb_modeswitch is handling those now AFAIK.
>
> So if we do this in userspace, I think usb_modeswitch is not a bad
> choice.
Ok, that's interesting... I tinkered with usb_modeswitch a bit and I
made it switch the G920 just fine after a while. Consider the patches
dropped then, letting usb_modeswitch take care of this sounds
reasonable.
Michal
Powered by blists - more mailing lists