From: Oliver Neukum <oliver@neukum.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Dan Williams <dcbw@redhat.com>,
Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
Frank Schaefer <schaefer.frank@gmx.net>,
linux-wireless@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] ar9170usb: add mode-switching for AVM Fritz!WLAN USB N devices in cdrom mode
Date: Tue, 3 Nov 2009 17:29:25 +0100 [thread overview]
Message-ID: <200911031729.26463.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0911031001470.10778-100000@netrider.rowland.org>
Am Dienstag, 3. November 2009 16:16:12 schrieb Alan Stern:
> This sounds as if you are trying very hard to get the _worst_ of both
> worlds! You would force users to upgrade their kernels before they can
> use new devices (because the kernel is where the mode-switch code will
> be), and you also would force them to upgrade their userspace settings
> (so that the new mode-switch code will be called).
Yes.
> I'm with Matt Dharm and Josua Dietze on this. Jobs that can be handled
> in userspace _should_ be handled there.
There is the inconvenient problem of hibernation. And, if more systems
start cutting power to USB in STR, the problem of STR. I am inclined
to declare that hibernation is a problem of those pesky misdesigns.
But dare we say that also about STR?
Regards
Oliver
next prev parent reply other threads:[~2009-11-03 16:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200910171606.02961.oliver@neukum.org>
[not found] ` <Pine.LNX.4.44L0.0910171130550.25594-100000@netrider.rowland.org>
[not found] ` <20091017220313.GH24502@one-eyed-alien.net>
[not found] ` <4ADC3657.6080906@gmx.net>
2009-11-01 18:00 ` [PATCH] ar9170usb: add mode-switching for AVM Fritz!WLAN USB N devices in cdrom mode Frank Schaefer
2009-11-01 18:27 ` Johannes Berg
2009-11-01 20:02 ` Frank Schaefer
2009-11-01 18:29 ` Josua Dietze
2009-11-01 18:35 ` Matthew Dharm
2009-11-01 20:24 ` Frank Schaefer
2009-11-01 20:49 ` Christian Lamparter
2009-11-02 20:16 ` Frank Schaefer
2009-11-02 0:47 ` Matthew Dharm
2009-11-02 20:07 ` Frank Schaefer
2009-11-02 21:10 ` Matthew Dharm
2009-11-02 21:15 ` Matthew Dharm
2009-11-03 20:33 ` Frank Schaefer
2009-11-01 20:11 ` Frank Schaefer
2009-11-02 0:51 ` Matthew Dharm
2009-11-02 20:10 ` Frank Schaefer
2009-11-02 20:18 ` Dan Williams
2009-11-02 21:05 ` Alan Cox
2009-11-02 21:37 ` Dan Williams
2009-11-02 21:45 ` Dan Williams
2009-11-02 22:23 ` Christian Lamparter
2009-11-03 20:22 ` Frank Schaefer
2009-11-02 21:11 ` Matthew Dharm
2009-11-02 21:42 ` Dan Williams
2009-11-02 22:39 ` Alan Cox
2009-11-03 0:54 ` Dan Williams
2009-11-03 10:55 ` Oliver Neukum
2009-11-03 15:16 ` Alan Stern
2009-11-03 16:29 ` Oliver Neukum [this message]
2009-11-03 22:47 ` Alan Stern
2009-11-03 23:55 ` Oliver Neukum
2009-11-04 3:57 ` Alan Stern
2009-11-04 9:11 ` Oliver Neukum
2009-11-03 20:42 ` Frank Schaefer
2009-11-04 16:16 ` Alan Stern
2009-11-04 16:25 ` Johannes Berg
2009-11-04 17:07 ` Alan Stern
2009-11-04 17:41 ` Josua Dietze
2009-11-04 16:41 ` Oliver Neukum
2009-11-04 17:41 ` Josua Dietze
2009-11-03 10:57 ` Oliver Neukum
2009-11-03 12:58 ` Christian Lamparter
2009-11-03 20:18 ` Frank Schaefer
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=200911031729.26463.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=dcbw@redhat.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=schaefer.frank@gmx.net \
--cc=stern@rowland.harvard.edu \
/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).