From: Thierry Reding <thierry.reding@avionic-design.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 7/7] tegra: Add Tamonten Evaluation Carrier support
Date: Mon, 11 Jun 2012 11:22:58 +0200 [thread overview]
Message-ID: <20120611092258.GB31441@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <20120608203831.GO13311@nvidia.com>
* Allen Martin wrote:
> On Mon, Jun 04, 2012 at 11:02:30PM -0700, Thierry Reding wrote:
> > The Tamonten Evaluation Carrier is an evaluation board for the Tamonten
> > processor board. More information is available here:
> >
> > http://www.avionic-design.de/en/products/nvidia-tegra-tamonten-system-en/nvidia-tegra-tamonten-evboard-en.html
> >
> > Signed-off-by: Thierry Reding <thierry.reding@avionic-design.de>
> > Acked-by: Stephen Warren <swarren@wwwdotorg.org>
> > ---
> > diff --git a/include/configs/tec.h b/include/configs/tec.h
> > new file mode 100644
> > index 0000000..3d0a788
> > --- /dev/null
> > +++ b/include/configs/tec.h
> > +
> > +#define CONFIG_BOOTCOMMAND \
> > + "mmc rescan;" \
> > + "ext2load mmc 0 0x17000000 /boot/uImage;" \
> > + "bootm"
> > +
> > +#endif /* __CONFIG_H */
>
> You're not including "tegra2-common-post.h" here, is that on purpose?
> I think it's preferable if all tegra boards include both
> tegra2-common and tegra2-common-post to make it easier to apply
> changes across the board.
Yes, that was on purpose. I still need to figure out if I want to use
Stephen's boot commands as defined in tegra2-common-post.h. But I just
realized that since our boards define CONFIG_BOOTCOMMAND, including it
won't hurt much anyway. I also just noticed that Stephen added it for
Medcom and Plutux already and I'm fine with you carrying the TEC change
in your series.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120611/9aebf5b0/attachment.pgp>
prev parent reply other threads:[~2012-06-11 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 6:02 [U-Boot] [PATCH v3 1/7] tegra: Rework Tamonten support Thierry Reding
2012-06-05 6:02 ` [U-Boot] [PATCH v3 2/7] tegra: medcom: Add device tree support Thierry Reding
2012-06-05 6:02 ` [U-Boot] [PATCH v3 3/7] tegra: plutux: " Thierry Reding
2012-06-05 6:02 ` [U-Boot] [PATCH v3 4/7] tegra: Allow boards to perform early GPIO setup Thierry Reding
2012-06-05 6:02 ` [U-Boot] [PATCH v3 5/7] tegra: Implement gpio_early_init() on Tamonten Thierry Reding
2012-06-05 6:02 ` [U-Boot] [PATCH v3 6/7] tegra: Use SD write-protect GPIO " Thierry Reding
2012-06-05 6:02 ` [U-Boot] [PATCH v3 7/7] tegra: Add Tamonten Evaluation Carrier support Thierry Reding
2012-06-08 20:38 ` Allen Martin
2012-06-11 9:22 ` Thierry Reding [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=20120611092258.GB31441@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--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