From: Josua Dietze <digidietze@draisberghof.de>
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
usb-storage@lists.one-eyed-alien.net,
Stefan Seyfried <seife@sphairon.com>
Subject: Re: [PATCH] move eject code from zd1211rw to usb-storage
Date: Tue, 15 Dec 2009 15:59:15 +0100 [thread overview]
Message-ID: <4B27A443.6040908@draisberghof.de> (raw)
In-Reply-To: <20091215150137.46bd9817@strolchi.home.s3e.de>
Stefan Seyfried schrieb:
> But given that there is already an "option_zero_cd" parameter in
> usb-storage, it should be easy to massage this into a general "do not
> eject virtual installer media" flag so that people are still able to
> get the windows driver files off their devices should they need to do
> so.
>
>> I'd like to see these devices removed from unusual_devs.h.
>
> I'd like them to work with one driver, not two (one in kernel and one
> in userspace).
The more basic arguments that prevailed at the last time such an
"eject" command was being considered for inclusion into usb-storage
were:
1. Userspace can obviously react a lot quicker than kernel space to
new or changed devices popping up.
2. Userspace works with older kernels immediately.
> That's a fundamental difference in opinions, and I fear I'm not the one
> who is going to decice how this will be handled ;)
Neither am I. But the number of known mode-switching USB devices is
now at around 50. New ones are arriving by the month or even week.
A decision to handle *all of them* in usb-storage would lead to the
disadvantages pointed out.
A decision to handle just *some of them* can hardly be made
plausible if there are no immediate technical reasons.
Oh, and in most cases (including your suggestion) there *are*
already two drivers necessary to make these devices work,
independent of where the switching is happening ...
> Have fun,
You too!
Josh
--
Man is the only creature on earth enabled to take a
warm meal while flying! Loriot
next prev parent reply other threads:[~2009-12-15 14:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 12:06 [PATCH] move eject code from zd1211rw to usb-storage Stefan Seyfried
2009-12-15 12:31 ` Josua Dietze
2009-12-15 14:01 ` Stefan Seyfried
2009-12-15 14:59 ` Josua Dietze [this message]
2009-12-15 17:58 ` [usb-storage] " Matthew Dharm
2009-12-15 15:11 ` Oliver Neukum
2009-12-15 18:03 ` Matthew Dharm
2009-12-16 10:29 ` Oliver Neukum
2009-12-16 11:42 ` Josua Dietze
2009-12-16 18:03 ` Matthew Dharm
2009-12-16 19:50 ` Dan Williams
2009-12-16 19:52 ` Matthew Dharm
2009-12-17 13:02 ` Oliver Neukum
2009-12-17 13:33 ` Josua Dietze
2009-12-17 14:36 ` Oliver Neukum
2009-12-17 15:22 ` Josua Dietze
2009-12-17 18:21 ` Matthew Dharm
2009-12-16 10:49 ` Stefan Seyfried
2009-12-16 11:22 ` Josua Dietze
2009-12-16 12:14 ` Stefan Seyfried
2009-12-16 14:05 ` John W. Linville
2009-12-16 16:47 ` Dan Williams
2009-12-16 19:12 ` Matthew Dharm
2009-12-16 11:23 ` Oliver Neukum
2009-12-17 10:41 ` [usb-storage] " Daniel Drake
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=4B27A443.6040908@draisberghof.de \
--to=digidietze@draisberghof.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=seife@sphairon.com \
--cc=stefan.seyfried@googlemail.com \
--cc=usb-storage@lists.one-eyed-alien.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.