| 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
| ||
|
Message-ID: <44F85646.4030100@mauve.plus.com> Date: Fri, 01 Sep 2006 16:48:22 +0100 From: Ian Stirling <ian.stirling@...ve.plus.com> To: Pierre Ossman <drzeus-list@...eus.cx> CC: madhu chikkature <crmadhu210@...il.com>, linux-kernel@...r.kernel.org Subject: Re: SDIO card support in Linux Pierre Ossman wrote: > madhu chikkature wrote: >> Hi, >> >> This is regarding the discussion going on in the list about the >> support of SDIO cards in Linux. I read some discussion happening to >> support SDIO cards using the existing Linux MMC core but I could not >> figure out what would be the direction the community to support the >> SDIO cards. <snip> >> With this, is it a fissible solution to have the MMC core do the >> initialization part of the card by having the CMD sequence for SDIO >> card (CMD5 and CMD3) in the mmc_setup sequence and maintain the SDIO >> card list along with MMC/SD? >> > > SD mandates a star topology (just a single card per bus), so we'll just > force a single card into the list. SD memory cards can actually work on > a shared bus, SDIO can not. It's not a big problem in practice though. Is this true in SD-1 bit mode, or SPI? I see nothing on a quick read-through of the abbreviated SDIO spec precluding this. Of course, it'd mean wire-or'd interrupt lines. - 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/
Powered by blists - more mailing lists