From: Alex Dubov <oakad@yahoo.com>
To: Carlos Corbacho <carlos@strangeworlds.co.uk>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
drzeus@drzeus.cx
Subject: Re: [PATCH] [MEMSTICK] Initial commit for Sony MemoryStick support
Date: Sun, 30 Dec 2007 17:01:08 -0800 (PST) [thread overview]
Message-ID: <250570.28220.qm@web36706.mail.mud.yahoo.com> (raw)
In-Reply-To: <200712310001.15395.carlos@strangeworlds.co.uk>
> However, my only concerns are that:
>
> 1) tifm_ms was not autoloaded
> 2) On loading tifm_ms, only memstick was autoloaded - mspro_block was not.
>
> Although, whether this is an issue with userspace (ie. udev) not dealing with
> the modules properly, I don't know.
>
This is exactly the same as with tifm_sd module if you noticed.
First, there are no modaliases for tifm (I was thinking to add them later, when at least two card
types are supported, if at all), so the appropriate udev rule should be added (similar to the sd
one).
Second, it is impossible to guess in advance, which type of card is put into slot (Pro, legacy or
IO of either sort). Same as mmc_block, actually. The only way to get it autoloaded, is, again,
with appropriate udev rule (uevent is emitted when card type is detected).
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
next prev parent reply other threads:[~2007-12-31 1:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-24 3:06 oakad
2007-12-31 0:01 ` Carlos Corbacho
2007-12-31 0:31 ` Jan Engelhardt
2007-12-31 0:54 ` Alex Dubov
2007-12-31 0:56 ` Carlos Corbacho
2007-12-31 1:01 ` Alex Dubov [this message]
2007-12-31 1:15 ` Carlos Corbacho
2007-12-31 4:51 ` Alex Dubov
2008-01-02 6:42 oakad
2008-01-10 9:00 ` Andrew Morton
2008-01-11 12:14 ` Jens Axboe
2008-01-14 3:26 ` Alex Dubov
2008-01-22 16:12 ` Alex Dubov
2008-01-22 18:59 ` Andrew Morton
2008-01-15 17:21 ` Mariusz Kozlowski
2008-01-16 1:52 ` Alex Dubov
2008-01-13 22:47 Miguel Botón
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=250570.28220.qm@web36706.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=carlos@strangeworlds.co.uk \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®