From: popcorn mix <popcornmix@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] usb: dwc2: handle bcm2835 phys->virt address translations
Date: Tue, 17 Mar 2015 17:53:47 +0000 [thread overview]
Message-ID: <55086A2B.30506@gmail.com> (raw)
In-Reply-To: <5508646C.5040802@wwwdotorg.org>
On 17/03/15 17:29, Stephen Warren wrote:
> Do the RPi 1 and RPi 2 use different kernel binaries in the RPi Foundation's images? I'd assumed there was a single unified binary which supported both. The reason I ask is that I see:
We ship separate kernel binaries (kernel.img for 2835 and kernel7.img for 2836).
kernel.img is built from bcmrpi_defconfig, and kernel7.img is built from bcm2709_defconfig
A single unified binary would sure be nice, but I think we have too many non-device-tree drivers in our kernel and not enough experience to make this happen easily.
It's certainly a desirable goal (as it moving closer to the upstream mach-2835 kernel).
> I assume the SDHCI controller (RPi SD card, CM eMMC) is affected by this just as much; we need to use bus addresses not ARM physical addresses when programming any DMA there?
Yes. Any address given to the DMA controller should be a bus address.
Similarly any address exchanged with the GPU (e.g. framebuffer address from mailbox interface) should be a bus address.
> Perhaps this would explain why I had issues with the eMMC on the CM (I think only in the kernel though, whereas U-Boot may have been fine; I'll have to check)
Using physical addresses when bus addresses are required can almost work, but with intermittent failure cases, so yes that sounds possible.
> I assume 128M and 512M there should be 128K and 512K?
Yes, quite right.
next prev parent reply other threads:[~2015-03-17 17:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 6:13 [U-Boot] [RFC PATCH] usb: dwc2: handle bcm2835 phys->virt address translations Stephen Warren
2015-03-13 14:30 ` Marek Vasut
2015-03-13 16:35 ` Stephen Warren
2015-03-13 18:13 ` Marek Vasut
2015-03-13 18:39 ` Stephen Warren
2015-03-13 18:49 ` Marek Vasut
2015-03-13 17:02 ` Eric Anholt
2015-03-15 16:04 ` Stephen Warren
2015-03-15 18:20 ` Marek Vasut
2015-03-17 3:04 ` Stephen Warren
2015-03-17 14:57 ` popcorn mix
2015-03-17 17:29 ` Stephen Warren
2015-03-17 17:53 ` popcorn mix [this message]
2015-03-15 16:51 ` Stephen Warren
2015-03-15 18:20 ` Marek Vasut
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=55086A2B.30506@gmail.com \
--to=popcornmix@gmail.com \
--cc=u-boot@lists.denx.de \
/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