All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Dubov <oakad@yahoo.com>
To: Sergey Yanovich <ynvich@gmail.com>
Cc: linux-kernel@vger.kernel.org, Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7
Date: Mon, 23 Apr 2007 06:16:16 -0700 (PDT)	[thread overview]
Message-ID: <90215.57597.qm@web36713.mail.mud.yahoo.com> (raw)
In-Reply-To: <5a04609e0704230029x56f08654v9d9d3fb1fef414ee@mail.gmail.com>


--- Sergey Yanovich <ynvich@gmail.com> wrote:

> > > For a typical, non-linux-geek user there are just two states of the device -
> > > available and not available. Ububtu is famous for its end-user support.
> > > They ship your driver since linux-2.6.17. But they pack it in one module.
> > > And that is _much_ easier, then a hotplug script.
> >
> > No, we ship a udev script.
> 
> OK, me bad for using the present tense. But you had a single module
> in Oct 2006, didn't you? And maybe, you would like to post the script.

Here's a simple udev rule that will do what you want:

SUBSYSTEM=="tifm", ACTION=="add", TIFM_CARD_TYPE=="SD", RUN+="/sbin/modprobe tifm_sd"

(just stick it somewhere in the udev rules).

You shall take into consideration that mmc currently lacks uevent support, so mmc_block must be
loaded manually (this is a long pending todo thingy; supposedly it waits for the first sdio
driver). There's no direct dependency of tifm_sd on mmc_block (only on mmc_core).

May be I'll add a modalias entry later so the explicit rule will not be needed.

As a side note: I have some very good reasons for the current driver architecture. You may want to
look them up in the mail archive (I outlined them during the initial driver submission).


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

  reply	other threads:[~2007-04-23 13:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4627D402.8020107@gmail.com>
2007-04-20  2:17 ` [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7 Alex Dubov
2007-04-20  8:20   ` Brad Campbell
2007-04-20  8:31     ` Fabio Comolli
2007-04-20 10:10       ` Sergey Yanovich
2007-04-22  1:34 ` Alex Dubov
2007-04-22 12:15   ` Sergey Yanovich
2007-04-23  7:04     ` Matthew Garrett
2007-04-23  7:29       ` Sergey Yanovich
2007-04-23 13:16         ` Alex Dubov [this message]
2007-04-23 14:12           ` Sergey Yanovich
2007-04-24  2:55             ` Alex Dubov
2007-04-24  8:05               ` Sergey Yanovich
2007-04-26  6:36 ` Pierre Ossman
2007-04-27  2:41   ` Alex Dubov
2007-04-27  7:50     ` Sergey Yanovich
2007-04-27 11:23       ` Alex Dubov
2007-04-27 12:14         ` Sergey Yanovich
2007-04-27 16:55           ` Alex Dubov
2007-04-27 18:36             ` Sergey Yanovich
2007-04-28  8:10               ` Alex Dubov
2007-04-28  8:41                 ` Sergey Yanovich
2007-04-28  9:08                   ` Sergey Yanovich
2007-04-28 11:34               ` Pierre Ossman
2007-04-28 11:44                 ` Alex Dubov
2007-04-28 17:07                   ` Sergey Yanovich
2007-04-19 20:53 Sergey Yanovich
2007-04-19 22:56 ` Arnd Bergmann
2007-04-20  9:22   ` Sergey Yanovich

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=90215.57597.qm@web36713.mail.mud.yahoo.com \
    --to=oakad@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=ynvich@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.