> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
