From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Tegra: T30: Beaver: Fix board/board_name env vars, s/b beaver, not cardhu
Date: Wed, 17 Apr 2013 09:50:47 -0600 [thread overview]
Message-ID: <516EC4D7.5040705@wwwdotorg.org> (raw)
In-Reply-To: <1366212139-30881-1-git-send-email-twarren@nvidia.com>
On 04/17/2013 09:22 AM, Tom Warren wrote:
> Did a 'strings u-boot-dtb-tegra.bin | less' and saw that both
> board and board_name == beaver. Didn't test as I have no T30
> Beaver board here.
Tested-by: Stephen Warren <swarren@nvidia.com>
Reviewed-by: Stephen Warren <swarren@nvidia.com>
I guess this is about the only way to do it; I checked
include/autoconf.mk and, and there's no variable that says "beaver" when
the beaver entry in boards.cfg is based on cardhu, and I'm sure we'll
need some separate code later anyway, so there's no harm adding the
makefile now.
prev parent reply other threads:[~2013-04-17 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 15:22 [U-Boot] [PATCH] Tegra: T30: Beaver: Fix board/board_name env vars, s/b beaver, not cardhu Tom Warren
2013-04-17 15:50 ` Stephen Warren [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=516EC4D7.5040705@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