linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Schaefer <schaefer.frank@gmx.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ar9170usb: add mode-switching for AVM Fritz!WLAN USB N devices in cdrom mode
Date: Mon, 02 Nov 2009 21:16:27 +0100	[thread overview]
Message-ID: <4AEF3E1B.9060106@gmx.net> (raw)
In-Reply-To: <200911012149.57966.chunkeey@googlemail.com>

Christian Lamparter schrieb:
> On Sunday 01 November 2009 21:24:28 Frank Schaefer wrote:
>   
>> Matthew Dharm schrieb:
>>     
>>> On Sun, Nov 01, 2009 at 07:29:20PM +0100, Josua Dietze wrote:
>>>       
>>>> Frank Schaefer schrieb:   
>>>>         
>>>>> I really think the mode-switching should be done in the kernel and not
>>>>> in user-space for reasons of usability.
>>>>>           
>>>> What is wrong with an udev rule entry? By the way, did the "eject" 
>>>> command line tool work as well?
>>>>         
>>> And I think it should be done in userspace for issues of maintainability
>>> and useability.  It is much easier for users to upgrade their udev then
>>> their kernel.
>>>       
>> Maintainability for whom ? The kernel-devs or the distro-people and the
>> users ? ;)
>>
>> Please think about the users. They don't know that they have to create
>> udev-rules or have to install additional packages like usb_modeswitch
>> (which is nevertheless a great tool !).
>> And even if they know, they don't want to do that. So it's up to the
>> distros to do this automatically, which will in reality never come true
>> for all devices and distros.
>>     
> yes, please think about the users!
>
> All not-so-trival-changes have to go through wireless-testing / wireless-next,
> net-next, linux-next until it hits finally the mainline... And then only users
> which are able to update their kernels will benefit, *everyone else* has
> to wait until their distros to pick up the new kernel... this could be easily more
> than a year before the device will work right out of the box for *everyone else*.
>   
Which potential not-so-trivial-changes do you think of in this case ?
And userspace-software + packages have a quality-assurance-procedure,
too, right ? ;)
> Therefore udev should be the way to go...
Maybe it should be, but it's a solution which will never work
satisfyingly. At least as long as the needed udev-rules are not shipped
with the kernel...
>  and as a bonus: a userspace/udev solution 
> does work with older kernels right away!
>
> Regards,
> 	Chr
Frank


  reply	other threads:[~2009-11-02 20:16 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 [this message]
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
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=4AEF3E1B.9060106@gmx.net \
    --to=schaefer.frank@gmx.net \
    --cc=chunkeey@googlemail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).