From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH U-Boot] ARM: rpi_b: detect board revision
Date: Wed, 19 Nov 2014 10:43:56 -0700 [thread overview]
Message-ID: <546CD6DC.1020404@wwwdotorg.org> (raw)
In-Reply-To: <1416372021-17997-1-git-send-email-swarren@wwwdotorg.org>
On 11/18/2014 09:40 PM, Stephen Warren wrote:
> Detect the board revision early during boot, and print the decoded
> model name.
>
> Eventually, this information can be used for tasks such as:
> - Allowing/preventing USB device mode; some models have a USB device on-
> board so only host mode makes sense. Others connect the SoC directly
> to the USB connector, so device-mode might make sense.
> - The on-board USB hub/Ethernet requires different GPIOs to enable it,
> although luckily the default appears to be fine so far.
> - The compute module contains an on-board eMMC device, so we could store
> the environment there. Other models use an SD card and so don't support
> saving the environment (unless we store it in a file on the FAT boot
> partition...)
>
> Set $fdtfile based on this information. At present, the mainline Linux
> kernel doesn't contain a separate DTB for most models, but I hope that
> will change soon.
BTW, I should have mentioned that I'm hoping the kernel people CC'd here
will take a look at the DTB filenames this patch assumes, and comment on
whether they seem reasonable. If so, we can formulate a patch for the
kernel to actually create all those DTs in the nearish future.
next prev parent reply other threads:[~2014-11-19 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 4:40 [U-Boot] [PATCH U-Boot] ARM: rpi_b: detect board revision Stephen Warren
2014-11-19 17:43 ` Stephen Warren [this message]
2014-11-19 18:22 ` Matthias Klein
2014-11-24 15:50 ` Simon Glass
2014-11-25 3:38 ` Stephen Warren
2014-11-25 3:48 ` Simon Glass
2015-07-24 6:26 ` Stephen Warren
2015-08-02 21:29 ` Simon Glass
2014-12-08 21:41 ` [U-Boot] [U-Boot,U-Boot] " Tom Rini
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=546CD6DC.1020404@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