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-next>] [day] [month] [year] [list]

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

Hi David.

First, my original post on LKML on the subject of MMC/SD over SPI framwork:

http://lkml.org/lkml/2006/8/1/71

I began developing a driver for MMC access over SPI on the Analog Devices 
Blackfin DSPs, running uClinux this spring. However, since then the blackfin 
uClinux has moved from kernel version 2.6.12 to 2.6.16 with the unified SPI 
framework. Also, a platform spi driver for the ADI Blackfin was recently 
written. I released my driver to the Blackfin uClinux community a few weeks 
ago and my plans was to move over to the SPI framwork using the platform 
driver instead of low level blackfin SPI related code.

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?

My current goal was to make my driver platform independent and then(if 
possible) connect to the MMC subsystem which i, at this point is not too 
familiar with.

regards

Hans Eklund
Rubico AB - http://www.rubico.se
Sweden.
-
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/