linux-kernel - Re: Block request processing for MMC/SD over SPI bus

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]

Date:	Tue, 1 Aug 2006 07:45:39 -0700
From:	David Brownell <david-b@...bell.net>
To:	hans@...ico.se
Cc:	linux-kernel@...r.kernel.org,
	Russell King <rmk+lkml@....linux.org.uk>
Subject: Re: Block request processing for MMC/SD over SPI bus

On Tuesday 01 August 2006 3:08 am, Hans Eklund wrote:

> As you can see om my LKML post, my driver covers (at first stage) everything 
> from low level SPI commands and block device insertion to the request 
> processing(since i at first could not connect to the MMC subsystem). Now, 
> Russel King believes that you may have written a SPI to MMC subsytem driver. 
> Correct? If so, whats the status on your driver?

Not entirely "my" driver, I just updated it and got it to partially enumerate
on some hardware that's a bit too weak for "real work":

http://sourceforge.net/mailarchive/forum.php?thread_id=13335072&forum_id=45866

... and there's the separate issue of the spi_claim()/spi_release() API
to take over an entire bus.  Such an API could be used by other SPI based
interfaces; some in-system-programmers (including JTAG) need that same kind
of protocol tweaking hook for SPI.

- Dave

-
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/