linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josua Dietze <digidietze@draisberghof.de>
To: Oliver Neukum <oliver@neukum.org>
Cc: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
	Stefan Seyfried <stefan.seyfried@googlemail.com>,
	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: Wed, 16 Dec 2009 12:42:16 +0100	[thread overview]
Message-ID: <4B28C798.502@draisberghof.de> (raw)
In-Reply-To: <200912161129.27284.oliver@neukum.org>

Oliver Neukum schrieb:

> Am Dienstag, 15. Dezember 2009 19:03:00 schrieb Matthew Dharm:
>>> This would break existing systems and thus introduce a regression.
>>> We'd need to go through a feature removal process. For the time being
>>> I see no alternative to Seife's patch, as we cannot introduce ejection
>>> code to another wireless driver and need to support these devices.
>> The right answer here is neither to move the eject code nor to introduce
>> more of it.  New devices should be supported via userspace.
> 
> Usually I would agree, but in this case the vendor reused IDs.
> The legacy kernel space switcher and user space would race.

User space can test for device/interface class (which will 
supposedly change even if the IDs do not) and base it's actions on 
that. It was done before.

Apart from that issue, I can see that there is a problem with a 
device that has worked without "external" handling up to now. 
Unfortunately, I can't think about a clean solution.

Josua
-- 
Man is the only creature on earth enabled to take a
warm meal while flying!                      Loriot

  reply	other threads:[~2009-12-16 11:42 UTC|newest]

Thread overview: 24+ 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
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 [this message]
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 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=4B28C798.502@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=mdharm-kernel@one-eyed-alien.net \
    --cc=oliver@neukum.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 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).