From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3] omap3: overo: Select fdtfile for expansion board
Date: Thu, 19 Jun 2014 18:02:12 -0400 [thread overview]
Message-ID: <20140619220212.GV20480@bill-the-cat> (raw)
In-Reply-To: <1402426956-21108-1-git-send-email-ashcharles@gmail.com>
On Tue, Jun 10, 2014 at 12:02:36PM -0700, Ash Charles wrote:
> The u-boot Overo board actually supports both Overo (OMAP35xx)
> and Overo Storm (AM/DM37xx) COMs with a range of different expansion
> boards. This provides a mechanism to select the an appropriate device
> tree file based on the processor version and, if available, the
> expansion board ID written on the expansion board EEPROM. To match the
> 3.15+ kernels, fdtfile names have this format:
> "omap3-overo[-storm]-<expansion board name>.dtb"
>
> By default, we use "omap3-overo-storm-tobi.dtb".
>
> Signed-off-by: Ash Charles <ashcharles@gmail.com>
Applied to u-boot-ti/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140619/762f380c/attachment.pgp>
prev parent reply other threads:[~2014-06-19 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 18:37 [U-Boot] [PATCH] omap3: overo: Select fdtfile for expansion board Ash Charles
2014-06-07 14:29 ` Stefan Herbrechtsmeier
2014-06-07 17:48 ` Tom Rini
2014-06-07 20:11 ` Ash Charles
2014-06-08 7:57 ` Stefan Herbrechtsmeier
2014-06-09 20:47 ` Ash Charles
2014-06-09 20:47 ` [U-Boot] [Patch v2] " Ash Charles
2014-06-10 7:30 ` Stefan Herbrechtsmeier
2014-06-10 17:17 ` Ash Charles
2014-06-10 18:06 ` Stefan Herbrechtsmeier
2014-06-10 19:00 ` Ash Charles
2014-06-10 19:02 ` [U-Boot] [Patch v3] " Ash Charles
2014-06-10 19:29 ` Stefan Herbrechtsmeier
2014-06-10 20:28 ` Ash Charles
2014-06-19 22:02 ` Tom Rini [this message]
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=20140619220212.GV20480@bill-the-cat \
--to=trini@ti.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