From: Alexander Aring <alex.aring@gmail.com>
To: barebox@lists.infradead.org
Subject: raspberry pi mmc issue
Date: Tue, 15 Oct 2013 13:51:17 +0200 [thread overview]
Message-ID: <20131015115116.GC2839@omega> (raw)
Hi all,
I using a not mainlined raspberry pi qemu implementation [1] and tried to
run barebox on it. All seems to working but if I probe the mmc with
mci0.probe=1 qemu will crash on a assert on 4 byte assert [2].
I dig a little bit into the Datasheet of bcm2835 [3] which says:
"Contrary to Arasan™’s documentation the EMMC module registers can only
be accessed as 32 bit registers, i.e. the two LSBs of the address are
always zero."
Then I dig into the barebox bcm2835_mci implementation and found
something [4]. We use there a readb on SDHCI_RESPONSE_0 which is not a
32 bit access. I just commented the if branch and it works.
Maybe this can make some errors on a real raspberry, too.
Maybe somebody knows a little bit more about mci and can help me to find
a proper solution? Perhaps just make a 32 bit access and do some bit
magic with masks and shifts?
- Alex
[1] https://github.com/Torlus/qemu-rpi
[2] https://github.com/Torlus/qemu/blob/rpi/hw/arm/bcm2835_emmc.c#L405
[3] http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf page 66
[4] http://git.pengutronix.de/?p=barebox.git;a=blob;f=drivers/mci/mci-bcm2835.c;h=abd38a35c9bfadcb2e3013eb4b220f74acf7464b;hb=HEAD#l264
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2013-10-15 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 11:51 Alexander Aring [this message]
2013-10-15 12:23 ` Sascha Hauer
2013-10-15 18:31 ` Alexander Aring
2013-10-15 18:39 ` Andre Heider
2013-10-16 7:23 ` Sascha Hauer
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=20131015115116.GC2839@omega \
--to=alex.aring@gmail.com \
--cc=barebox@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