From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: At91SAM9G20 AT91_MCI patches
Date: Fri, 30 Oct 2009 18:07:54 +0100 [thread overview]
Message-ID: <4AEB1D6A.9030606@atmel.com> (raw)
In-Reply-To: <5547BA931CA43849A16B2B02F2528D3938F80DD6@DEFTHW99E25MSX.ww902.siemens.net>
Retallack, Mark :
> Good morning, I hope this is the correct list.
>
> I am using the AT91SAM9G20-EK dev board. It does not look like the vanilla kernel (2.6.27+) contains the patch for support in the drivers/mmc/host/at91_mci.c file. Patch 5130/3 contains the correct information, however the final patch 5130/4 has the at91_mci section removed. Was there a reason for this?
>
> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=5130/3
> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=5130/4
I advice you to go with Linux4sam.org experimental patches for 2.6.27.
for 2.6.30 you have a preview here:
ftp://ftp.linux4sam.org/devel/linux/
(pick the 3 ones that are at91_mci related)
> Also it would be useful to know what the preferred MCI (MMC) driver for the AT91SAM9G20 is; the at91_mci or atmel_mci. The revision A and B AT91SAM9G20-EK dev board (board-sam9g20ek.c) uses the at91_mci driver, but the revision C AT91SAM9G20-EK dev board (board-sam9g20ek-2slot-mmc.c) uses atmel_mci driver.
Dual slot 9g20 has a patch to enable at91_mci use:
http://lists.infradead.org/pipermail/linux-arm-kernel/2009-October/002577.html
- atmel_mci allow the use of 2 slots but does not handle PDC (DMA data
transfers)
- at91_mci is using PDC (recommended with experimental patches mentioned
above)
Best regards,
--
Nicolas Ferre
prev parent reply other threads:[~2009-10-30 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 8:47 At91SAM9G20 AT91_MCI patches Retallack, Mark
2009-10-30 17:07 ` Nicolas Ferre [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=4AEB1D6A.9030606@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 NNTP newsgroup(s).