From: Stefan Sommerfeld <sommerfeld@mikrom.de>
To: Slide <slide.o.mix@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] SD/MMC Bus Driver
Date: Thu, 13 Jan 2011 09:51:00 -0000 [thread overview]
Message-ID: <4D2ECB07.2060300@mikrom.de> (raw)
In-Reply-To: <a623f7d11003222037k5537f8bby63ab2d6b487cea6e@mail.gmail.com>
Hi Slice
> I'm going to try my hand at writing an SD/MMC bus driver for eCos and
> contribute it. This will be the first real driver I've written for
> eCos and I'd like some pointers. I've looked at a few drivers in Linux
> and just code flows for the card initialization sequence and so forth.
> For a single SD/MMC controller on a chip, there can be multiple cards
> attached to the bus, and for a single chip, there can be multiple
> SD/MMC controllers. I am not quite sure how to represent this in the
> CDL and then the corresponding driver. I was thinking of defining a
> host driver and then having a CDL integer number for the number of
> SD/MMC controllers supported by the chip. Then, I was trying to figure
> out a way to tell the disk bus driver which of those controllers to
> check for cards.
>
> My other thought is to start out more simple and support a single
> controller on the chip and a single card attached to that controller,
> then it could be expanded from there. Any thoughts from the community?
>
Did you make any progress on this? I need a SD card driver for a i.MX51 (which
has a sd simplified interface) and I'm willing to write one.
Maybe you or anyone else already has something as starting point.
Bye...
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2011-01-13 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 3:38 Slide
2011-01-13 9:51 ` Stefan Sommerfeld [this message]
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=4D2ECB07.2060300@mikrom.de \
--to=sommerfeld@mikrom.de \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=slide.o.mix@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).