From: Robert Schwebel <r.schwebel@pengutronix.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ptxdist] u-boot-v2 rc7
Date: Wed, 25 Feb 2009 22:35:54 +0100 [thread overview]
Message-ID: <20090225213554.GV5367@pengutronix.de> (raw)
In-Reply-To: <49A5B278.7010300@lufkin.com>
On Wed, Feb 25, 2009 at 03:04:56PM -0600, John Jeffers wrote:
> In "~/u-boot-v2/board/pcm038/env/config
> (and in most other boards in v2)
>
> the following is found:
> /****+
> autoboot_timeout=3
>
> nfsroot="/ptx/work/octopus/rsc/svn/oselas/bsp/phytec/phyCORE-i.MX27/OSELAS.BSP-Phytec-phyCORE-i.MX27-trunk/root"
>
> bootargs="console=ttymxc0,115200"
> -****/
> I believe this causes certain scripting in ptxdist to fail "~>ptxdist
> test setenv<cr>" since it is setting up uboot configuration for Robert
> S.'s machine. It does not actually "hurt" u-boot-v2 rc7 since the
> knowledgeable user will make this go away for his board.
The automatic setup scripts in OSELAS.BSPs using this board should do
the right thing, the 'test setenv' script will push a well defined
environment into the box.
> Likely the community would be better served if there was a comment as
> the following:
>
> #really make sure this points to the nfs root source. Assuming the BSP
> was at the user home. ~>
> nfsroot="/OSELAS.BSP-Phytec-phyCORE-8/projectroot"
>
> It may be useful to fix this as a question to the user.//
Yes, good idea, please send a proper patch that fixes all of these
issues.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2009-02-25 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 21:04 [U-Boot] u-boot-v2 rc7 John Jeffers
2009-02-25 21:35 ` Robert Schwebel [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=20090225213554.GV5367@pengutronix.de \
--to=r.schwebel@pengutronix.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