LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Sergey Yanovich" <ynvich@gmail.com>
To: "Alex Dubov" <oakad@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7
Date: Sun, 22 Apr 2007 15:15:22 +0300 [thread overview]
Message-ID: <5a04609e0704220515h4049afas4dc98b90e66d1d16@mail.gmail.com> (raw)
In-Reply-To: <20070422013411.45105.qmail@web36709.mail.mud.yahoo.com>
Hi,
> > Finally, tifm_sd module needs to be manually inserted.
>
> By the way, the driver emits custom uevent when the new card is detected. I was going to look at
> this some day in the future, but if you want to mess a little with hotplug scripts the issue can
> be easily solved.
It would be nice if you to provide a sample script. Unfortunately,
hotplug scripts are distribution specific. And internal knowledge of
your modules is required to write one.
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.
And maybe, you would care to create a branch in you repository for
in-the-tree compiles.
> As I already said before, many of the complications exist because this is an universal adapter,
> and memorystick support is quite near in the queue.
The scope of your project is exceptionally wide. You plan to develop a whole
new layer for memorystick as a part.
At the same time, the [tifm_sd] code is device specific, and [tifm_7xx1]
code is also device specific. And both modules depend on the same device
(of family of devices). That makes me think that a bus/controller/slot
construction is not going to make thing any easier, but adds complexity.
In case of MMC/SD all abstraction has already been separated by the mmc
layer, in case of MS it is up to you, how to implement.
next prev parent reply other threads:[~2007-04-22 12:15 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 ` 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 [this message]
2007-04-23 7:04 ` Matthew Garrett
2007-04-23 7:29 ` Sergey Yanovich
2007-04-23 13:16 ` Alex Dubov
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=5a04609e0704220515h4049afas4dc98b90e66d1d16@mail.gmail.com \
--to=ynvich@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oakad@yahoo.com \
--subject='Re: [mmc] alternative TI FM MMC/SD driver for 2.6.21-rc7' \
/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
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).