linux-kernel - Re: [PATCH] [MEMSTICK] Initial commit for Sony MemoryStick support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200712310115.25455.carlos@strangeworlds.co.uk>
Date:	Mon, 31 Dec 2007 01:15:24 +0000
From:	Carlos Corbacho <carlos@...angeworlds.co.uk>
To:	Alex Dubov <oakad@...oo.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	drzeus@...eus.cx
Subject: Re: [PATCH] [MEMSTICK] Initial commit for Sony MemoryStick support

On Monday 31 December 2007 01:01:08 Alex Dubov wrote:
> This is exactly the same as with tifm_sd module if you noticed.

Unfortunately not, I've really never used tifm_sd as I don't have any MMC/ SD 
cards.

> Second, it is impossible to guess in advance, which type of card is put
> into slot (Pro, legacy or IO of either sort).

I imagined this to be the case.

> 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).

So do we require changes to the userspace udev rules here, or just some use of 
modalias in the drivers?

-Carlos
-- 
E-Mail: carlos@...angeworlds.co.uk
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/