From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: rpi_b: set $fdtfile in default environment
Date: Mon, 10 Feb 2014 22:46:53 -0700 [thread overview]
Message-ID: <52F9B94D.9030608@wwwdotorg.org> (raw)
In-Reply-To: <52F19FD7.60108@wwwdotorg.org>
On 02/04/2014 07:20 PM, Stephen Warren wrote:
> On 01/28/2014 10:41 PM, Stephen Warren wrote:
>> U-Boot names the Raspberry Pi board rpi_b. This means that the common
>> expression for DTB filename ${soc}-${board}.dtb expands to
>> bcm2835-rpi_b.dtb. However, the DTB generated by the Linux kernel is
>> bcm2835-rpi-b.dtb. Set $fdtfile in U-Boot's environment so that scripts
>> look for the correct DTB filename.
>>
>> An alternative would be to rename the U-Boot board to rpi-b. However,
>> that change would be far more invasive, and end up affecting users (i.e
>> they'd have to change their U-Boot build commands).
>
> Albert, does this look good?
Albert, is this patch OK? I also haven't heard anything back on:
4a97c0d ARM: bcm2835: fix mbox POWER_STATE_RESP_ON value
290cc12 ARM: rpi_b: rework boot scripts, enable sysboot
d7c3c9c ARM: rpi_b: load /uEnv.txt from MMC at startup
bae1449 ARM: rpi_b: convert to use distro defaults
f62463f pxe: allow compilation when !defined(CONFIG_CMD_NET)
11e1b89 ARM: bcm2835: config.mk isn't needed
b5cdf43 ARM: rpi_b: set $fdtfile in default environment
next prev parent reply other threads:[~2014-02-11 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 5:41 [U-Boot] [PATCH] ARM: rpi_b: set $fdtfile in default environment Stephen Warren
2014-02-05 2:20 ` Stephen Warren
2014-02-11 5:46 ` Stephen Warren [this message]
2014-02-11 12:38 ` Albert ARIBAUD
2014-02-13 14:02 ` Albert ARIBAUD
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=52F9B94D.9030608@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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