From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH v4] bootm: Add sub commands
Date: Wed, 08 Oct 2008 10:15:34 -0400 [thread overview]
Message-ID: <48ECC086.3050805@ge.com> (raw)
In-Reply-To: <391A4FFD-122B-40BB-BE53-75774FF764C9@kernel.crashing.org>
Kumar Gala wrote:
>
> On Oct 8, 2008, at 8:17 AM, Jerry Van Baren wrote:
>
>> Kumar Gala wrote:
>>> On Sep 29, 2008, at 8:49 AM, Jerry Van Baren wrote:
>>>> Kumar Gala wrote:
>>>>> On Sep 23, 2008, at 10:07 AM, Kumar Gala wrote:
>>>>>> * Use new find_cmd_tbl() to process sub-commands
>>>>>>
>>>>>> If this looks good I'll go ahead and clean it up for the other
>>>>>> arches and OSes.
>>>>>>
>>>>>> ---
>>>>>> common/cmd_bootm.c | 142 ++++++++++++++++++++++++++++-
>>>>>> include/image.h | 20 ++++-
>>>>>> lib_ppc/bootm.c | 262 +++++++++++++++++++++++++++++++++
>>>>>> +------------------
>>>>>> 3 files changed, 330 insertions(+), 94 deletions(-)
>>>>> Guys,
>>>>> Any comments on this?
>>>>> - k
>>>>
>>>> I didn't get to it over the weekend. Here in the North summer is a
>>>> fleeting thing to be savored while it lasts. :-/
>>> Any more feedback on this towards getting something into -next?
>>> - k
>>
>> Hi Kumar,
>>
>> I've been working on the micro side (the bootm [a-z]+ commands) and
>> the macro side (understanding cmd_bootm.c and image.c).
>>
>> I've been keeping notes on the denx.de wiki (inappropriately) on the
>> FDT page. They aren't entirely coherent either. :-/
>>
>> I applied your changeset and verified that the traditional bootm
>> syntax worked. I then tried to figure out a working sequence of bootm
>> [a-z]+ commands and failed.
>> <http://www.denx.de/wiki/view/U-Boot/UBootFdtInfo#Sequence>
>> * I didn't see any command for disabling interrupts
>
> You have to have the interrupt command built in. than you can do
> 'interrupts off'
Yup, I'll have to fix that.
>> * When I do the "bootm loados" command, my target (MPC8360EMDS) reboots
>> * Could be because interrupts are not disabled but we overwrite the
>> exception vectors.
>> * Could be I'm doing something wrong.
>
> this is most likely the case.
Kumar being kind. :-D
>> Do you have a boot script "use case" to illustrate a sequence that
>> works for you?
>
> yes, will post in a follow up.
Thanks, I'll run that tonight.
>> I have also been looking at the functions defined in cmd_bootm.c and
>> image.c. Image.c is HUGE. Cmd_bootm.c is pretty complex and part of
[snip]
> refactoring image.c is orthogonal to the functionality I'm trying to
> enable.
Yup. I took my eye off the ball.
Best regards,
gvb
next prev parent reply other threads:[~2008-10-08 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 15:07 [U-Boot] [RFC][PATCH v4] bootm: Add sub commands Kumar Gala
2008-09-29 13:39 ` Kumar Gala
2008-09-29 13:49 ` Jerry Van Baren
2008-10-08 6:04 ` Kumar Gala
2008-10-08 13:17 ` Jerry Van Baren
2008-10-08 13:45 ` Kumar Gala
2008-10-08 14:15 ` Jerry Van Baren [this message]
2008-10-08 13:51 ` [U-Boot] [RFC][PATCH v4] bootm: Add sub commands (sequence of commands to replicate bootm) Kumar Gala
2008-10-09 1:48 ` [U-Boot] [RFC][PATCH v4] bootm: Add sub commands Jerry Van Baren
2008-10-13 18:27 ` Kumar Gala
2008-10-13 19:14 ` Kumar Gala
2008-10-14 1:38 ` Jerry Van Baren
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=48ECC086.3050805@ge.com \
--to=gerald.vanbaren@ge.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