From: Hans Eklund <hans@rubico.se>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org, Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: Block request processing for MMC/SD over SPI bus
Date: Tue, 1 Aug 2006 12:08:27 +0200 [thread overview]
Message-ID: <200608011208.27143.hans@rubico.se> (raw)
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.
next reply other threads:[~2006-08-01 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 10:08 Hans Eklund [this message]
2006-08-01 14:45 ` Block request processing for MMC/SD over SPI bus David Brownell
2006-08-01 15:07 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2006-08-01 8:37 Hans Eklund
2006-08-01 8:42 ` Russell King
2006-08-08 15:07 ` Hans Eklund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608011208.27143.hans@rubico.se \
--to=hans@rubico.se \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox