From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] simplify bootm command
Date: Tue, 05 Aug 2008 06:02:11 -0400 [thread overview]
Message-ID: <48982523.4030706@gmail.com> (raw)
In-Reply-To: <467A628A-DCAA-4293-8571-C5ED10316EA3@kernel.crashing.org>
Kumar Gala wrote:
> If we really want to simplify what bootm does than I think we should
> remove ft_board_setup() from lib_ppc/bootm.c and expect any actually
> modification of the device tree to have already occurred.
>
> Is this something we'd really be willing to do?
>
> - k
I don't think so. We would horribly break backward compatibility and
make a severe mess for those trying to Just Ship Product[tm].
My current best thought is to create a new "boot simple" (boots?
bootsm?) command that contains only the essence of bootm. I would then
change the command "bootm" to do a hush script run of the env variable
"bootm" (i.e. the command "bootm" would really just be "run bootm").
The env variable "bootm" would then have to be created with the complex
(board/config appropriate) sequence that is currently hardcoded in the
command "bootm", with the last command being "boots", of course. This
would be selected by a new CONFIG_ configuration so that old boards
would go on as is until or unless the maintainer chose to move forward.
We probably would be able to auto-create the appropriate bootm script
string via the C preprocessor (ala the current "bootm" command), in
which case we could transparently replace the hardcoded "bootm" command
with a bootm script, remaining backwards compatible. I'm thinking the
New Improved[tm] "bootm" command would look for a "bootm" env variable
and, if it was not found, run a cpp-generated built-in script string
that implemented the present "bootm" sequence.
Best regards,
gvb
next prev parent reply other threads:[~2008-08-05 10:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 3:51 [U-Boot-Users] simplify bootm command Kumar Gala
2008-08-05 10:02 ` Jerry Van Baren [this message]
2008-08-05 10:19 ` Wolfgang Denk
2008-08-05 10:38 ` Jerry Van Baren
2008-08-05 11:05 ` Wolfgang Denk
2008-08-05 11:16 ` Albert ARIBAUD
2008-08-05 13:01 ` Wolfgang Denk
2008-08-05 13:45 ` Albert ARIBAUD
2008-08-05 12:15 ` Jerry Van Baren
2008-08-05 13:59 ` Detlev Zundel
2008-08-05 12:56 ` Kumar Gala
2008-08-05 13:36 ` Jerry Van Baren
2008-08-05 13:59 ` Kumar Gala
2008-08-05 14:08 ` Wolfgang Denk
2008-08-05 14:32 ` [U-Boot-Users] simplify bootm command -- deprecated or removing functionality? Kumar Gala
2008-08-05 14:45 ` Wolfgang Denk
2008-08-05 14:48 ` Kumar Gala
2008-08-05 15:05 ` [U-Boot-Users] simplify bootm command Kumar Gala
2008-08-05 16:11 ` Jerry Van Baren
2008-08-05 16:27 ` Kumar Gala
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=48982523.4030706@gmail.com \
--to=gvb.uboot@gmail.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