From: Robert Hancock <hancockrwd@gmail.com>
To: Robert Mykland <robert@ascenium.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB auto mount - specific versus general driver
Date: Sat, 11 Apr 2009 11:33:55 -0600 [thread overview]
Message-ID: <49E0D483.9040907@gmail.com> (raw)
In-Reply-To: <49E0127D.7030206@ascenium.com>
Robert Mykland wrote:
> Folks,
>
> Consider a USB key that auto mounts as a generic USB storage device
> using the block level driver for that. Can I write a driver that, for
> example, is more specific to that key and gets loaded and used at auto
> mount time instead of the generic driver? How would I go about
> identifying my driver so it superseded the generic one?
You'd have to add an unusual device entry to the USB storage driver
which tells it not to claim that device. Look at
drivers/usb/storage/unusual_devs.h and the US_FL_IGNORE_DEVICE flag.
>
> Thanks in Advance,
>
> -- Robert.
>
prev parent reply other threads:[~2009-04-11 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 3:46 USB auto mount - specific versus general driver Robert Mykland
2009-04-11 17:33 ` Robert Hancock [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=49E0D483.9040907@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robert@ascenium.com \
/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