linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: manuel.stahl@iis.fraunhofer.de (Manuel Stahl)
To: linux-arm-kernel@lists.infradead.org
Subject: atmel-mci / at91_mci
Date: Thu, 04 Feb 2010 09:57:51 +0100	[thread overview]
Message-ID: <4B6A8C0F.7080907@iis.fraunhofer.de> (raw)

Hi all,

I have a question regarding the atmel-mci/at91_mci driver merge. 
Actually I have an at91rm9200 device which get's an CRC error while 
inializing an SD-card. I guess it's because of an at91rm9200 errata:

- Data Endianess inversion from the MCI to MMC or SD Card

The at91_mci driver did some byte swapping in 'at91_mci_sg_to_dma' function.
Where would I implement this in the atmel-mci driver?

Attached is the kernel log when I insert a card.

Regards,
-- 

Dipl.-Inf. Manuel Stahl
Fraunhofer-Institut f?r Integrierte Schaltungen IIS
- Leistungsoptimierte Systeme -
Nordostpark 93                Telefon  +49 (0)911/58061-6419
90411 N?rnberg                Fax      +49 (0)911/58061-6398
http://www.iis.fraunhofer.de  manuel.stahl at iis.fraunhofer.de


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: atmel-mci.log
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100204/7dd51cd3/attachment-0001.el>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6148 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100204/7dd51cd3/attachment-0001.p7s>

             reply	other threads:[~2010-02-04  8:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04  8:57 Manuel Stahl [this message]
2010-02-08 13:13 ` atmel-mci / at91_mci Fabian Godehardt
2010-02-09 15:49   ` Manuel Stahl
2010-02-15 16:16     ` Sebastian Heutling
2010-02-22  9:56       ` Manuel Stahl

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=4B6A8C0F.7080907@iis.fraunhofer.de \
    --to=manuel.stahl@iis.fraunhofer.de \
    --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).