public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Elie De Brauwer <eliedebrauwer@gmail•com>
To: linuxppc-dev@lists•ozlabs.org
Subject: fsl-esdhc on P2020 weird endianess behavior
Date: Fri, 21 Jan 2011 17:22:08 +0100	[thread overview]
Message-ID: <4D39B2B0.9050207@gmail.com> (raw)

Hello list,

I have a P2020 processor on a custom board which uses the embedded 
fsl-esdhc controller. Hardware-wise this is functional and in u-boot 
everything seems to behave (mmc part 0 gives the correct partition table 
and ext2ls/fatls are capable of reading the contents of the sd card).

However as soon as I start Linux (2.6.36), I get all sorts of unwanted 
behavior. Linux is unable to detect the partition layout (but if I do a 
hexdump of the MBR, I see the endianness is swapped (last 4 bytes are aa 
55 00 00). Also when I try to obtain the card registers they show the 
same behavior:
# cat ./devices/soc.0/ff72e000.sdhci/mmc_host/mmc0/mmc0:0001/scr
0000b50200000000

While for comparison the same value on my (x86) laptop gives:
edb@lapedb:/sys/devices/pci0000:00/0000:00:1e.0/0000:15:00.2/mmc_host/mmc0/mmc0:0001$ 
cat scr
02b5000000000000

In my config I have the following set:
CONFIG_MMC_SDHCI=y
CONFIG_MMC_SDHCI_IO_ACCESSORS=y
CONFIG_MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER=y
# CONFIG_MMC_SDHCI_PCI is not set
CONFIG_MMC_SDHCI_OF=y
CONFIG_MMC_SDHCI_OF_ESDHC=y


any pointers are welcome.

gr
E.

-- 
Elie De Brauwer

             reply	other threads:[~2011-01-21 16:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 16:22 Elie De Brauwer [this message]
2011-01-24  3:26 ` fsl-esdhc on P2020 weird endianess behavior tiejun.chen
2011-01-24  7:52   ` Elie De Brauwer
2011-01-24  8:15     ` tiejun.chen
2011-01-24  9:03       ` Elie De Brauwer
2011-01-24  9:28         ` tiejun.chen
2011-01-24  9:36           ` Elie De Brauwer
2011-02-23 15:19 ` Elie De Brauwer

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=4D39B2B0.9050207@gmail.com \
    --to=eliedebrauwer@gmail$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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