linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: New rule for xD FTL driver
Date: Tue, 15 Jun 2010 03:19:34 +0000	[thread overview]
Message-ID: <20100615031933.GA11952@kroah.com> (raw)
In-Reply-To: <1276347244.4481.15.camel@maxim-laptop>

On Tue, Jun 15, 2010 at 02:55:49AM +0300, Maxim Levitsky wrote:
> On Mon, 2010-06-14 at 09:46 -0700, Greg KH wrote: 
> > On Sat, Jun 12, 2010 at 03:54:04PM +0300, Maxim Levitsky wrote:
> > > Hi,
> > > 
> > > I have written a driver for xD card reader and xD/SmartMedia FTL that is
> > > usually mandatory to use with xD cards.
> > > 
> > > I think this can be added to 80-drivers.rule
> > > SUBSYSTEM="mtd", RUN+="/sbin/modprobe sm_ftl"
> > 
> > Why does this module not have the proper MODULE_DEVICE() or aliases in
> > it so that you don't have to manually load the module?  This should not
> > need to be a udev rule.
> 
> Well mtd system is not using bus model.

Why not?  It should be fixed to do so.

> However a card needs to be probed (theoteticly) by several high-level
> FTL drivers to make one of them to bind to it. (In fact several can bind
> at same now, which is both bad and good feature).

Then why would you write a rule to automatically load the module on the
system no matter what?

> I understand that module can have aliases so it can bind to a bus.

module aliases are used by modprobe to know what module to load when a
device is found on a bus.

> Of course I can do a 'request_module', but I think it isn't nice thing
> to do.

Agreed.  But as it looks like you always want this module loaded, why
not just make it part of your mtd core?

thanks,

greg k-h

  parent reply	other threads:[~2010-06-15  3:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-12 12:54 New rule for xD FTL driver Maxim Levitsky
2010-06-14 16:46 ` Greg KH
2010-06-14 23:55 ` Maxim Levitsky
2010-06-15  3:19 ` Greg KH [this message]
2010-06-15 10:07 ` Maxim Levitsky
2010-06-15 10:28 ` David Woodhouse
2010-06-15 13:22 ` Maxim Levitsky
2010-06-15 14:55 ` Greg KH
2010-06-15 15:27 ` Maxim Levitsky
2010-06-15 15:45 ` Maxim Levitsky
2010-06-15 15:47 ` Greg KH
2010-06-15 16:05 ` Greg KH
2010-06-15 17:01 ` David Woodhouse
2010-06-15 17:19 ` Greg KH
2010-06-15 17:46 ` Maxim Levitsky
2010-06-15 19:02 ` Kay Sievers
2010-06-15 19:29 ` Maxim Levitsky
2010-06-17  9:38 ` Maxim Levitsky

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=20100615031933.GA11952@kroah.com \
    --to=greg@kroah.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;
as well as URLs for NNTP newsgroup(s).