Linux Hotplug development
 help / color / mirror / Atom feed
From: Rajkumar Manoharan <rmanoharan@atheros.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] rules: add udev rule for ath9k_htc (AR7010) device
Date: Mon, 13 Sep 2010 06:44:01 +0000	[thread overview]
Message-ID: <20100913063201.GA2407@vmraj-lnx.users.atheros.com> (raw)
In-Reply-To: <1284116300-9060-1-git-send-email-rmanoharan@atheros.com>

On Fri, Sep 10, 2010 at 04:50:01PM +0530, Kay Sievers wrote:
> On Fri, Sep 10, 2010 at 12:58, Rajkumar Manoharan
> <rmanoharan@atheros.com> wrote:
> > AR7010 cards detected as USB Mass storage mode by default and an eject
> > command is required to switch to wireless mode.
> 
> This has nothing to do with persistent device naming, and the core of
> udev can not be made device specific. It's installed on all
> architectures and systems, and therefore such hardware specific
> matches can not be in the default rule set.
> 
> Udev rules must not call any tools from /usr. Some packages do that,
> but the main udev package should not do that. Note, that I absolutely
> don't mind if people do that, because I think /usr must _never_ be on
> a separate partition.
> 
> Also the main udev package can not ship hardware specific rules,
> nobody will care about them, and they will no be maintained here and
> just bit-rot. Maybe it can go into the usb_modeswitch package, which
> does this eject thing for many other devices?
> 
> Thanks,
> Kay
Thanks for your input and the rule has been integrated into usb_modeswitch 
package.

Thanks,
Rajkumar

      parent reply	other threads:[~2010-09-13  6:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 10:57 [PATCH] rules: add udev rule for ath9k_htc (AR7010) device Rajkumar Manoharan
2010-09-10 11:20 ` Kay Sievers
2010-09-13  6:44 ` Rajkumar Manoharan [this message]

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=20100913063201.GA2407@vmraj-lnx.users.atheros.com \
    --to=rmanoharan@atheros.com \
    --cc=linux-hotplug@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