From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Tegra: T30: Beaver board support.
Date: Fri, 12 Apr 2013 16:39:50 -0600 [thread overview]
Message-ID: <51688D36.2060501@wwwdotorg.org> (raw)
In-Reply-To: <20130412223534.GX9914@bill-the-cat>
On 04/12/2013 04:35 PM, Tom Rini wrote:
> On Fri, Apr 12, 2013 at 03:30:39PM -0700, Tom Warren wrote:
>
>> Beaver is a Tegra30 board that is nearly 100% compatible
>> w/Cardhu. Add a Beaver build so it can begin to be
>> differentiated, if need be.
>>
>> Signed-off-by: Tom Warren <twarren@nvidia.com> ---
>> board/nvidia/beaver/Makefile | 38 +++++++++++++++++++++
>> board/nvidia/dts/tegra30-beaver.dts | 66
>> +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 +
>
> OK, I assume cardhu and beaver dts files differ, right? If so,
> maybe we can find a smaller way to just say we have N boards that
> use a different dts, but that's it?
I think you can do that just be modifying boards.cfg; n lines with the
same content except for the name in the first column, e.g.:
> snow arm armv7 smdk5250 samsung exynos
> smdk5250 arm armv7 smdk5250 samsung exynos
You can also add an extra column with options if needed, although I
imagine the makefiles can see the value of the first column to e.g.
select different .dts files?
Perhaps we should do the same for Seaboard/Ventana too.
next prev parent reply other threads:[~2013-04-12 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 22:30 [U-Boot] [PATCH] Tegra: T30: Beaver board support Tom Warren
2013-04-12 22:35 ` Tom Rini
2013-04-12 22:39 ` Stephen Warren [this message]
2013-04-12 22:40 ` Tom Warren
2013-04-13 0:50 ` 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=51688D36.2060501@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