public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC][PATCH 00/15] bootm refactoring
Date: Wed, 13 Aug 2008 01:31:27 -0400	[thread overview]
Message-ID: <48A271AF.6000508@gmail.com> (raw)
In-Reply-To: <1218575851-4404-1-git-send-email-galak@kernel.crashing.org>

Hi Kumar,

I'm on the road this week, so my ability to review code this week is 
suboptimal.  Having said that, this looks good!

Kumar Gala wrote:
> [PATCH 01/15] Update linux bootm to support ePAPR client interface
> [PATCH 02/15] add ability to disable ft_board_setup as part of bootm
> 
> possibly drop this patch if the boots method is acceptable

I don't follow what this remark is saying.

Is there a reason scripting in the "fdt boardsetup" command, eliminating 
the need to call ft_board_setup() as part of the bootm command chain?

> [PATCH 03/15] Clean up usage of icache_disable/dcache_disable
> [PATCH 04/15] fdt: added the ability to set initrd start/end via chosen command
> [PATCH 05/15] fdt: fdt addr w/o any args reports back the current working address
> [PATCH 06/15] bootm: refactor entry point code
> [PATCH 07/15] bootm: refactor ramdisk locating code
> [PATCH 08/15] bootm: refactor fdt locating and relocation code
> [PATCH 09/15] bootm: Set working fdt address as part of the bootm flow
> [PATCH 10/15] bootm: move lmb into the bootm_headers_t structure
> [PATCH 11/15] bootm: refactor image detection and os load steps
> [PATCH 12/15] fdt: refactor fdt resize code
> [PATCH 13/15] fdt: refactor initrd related code
> [PATCH 14/15] fdt: Added resize command
> [PATCH 15/15] boots: start of sub commands
> 
> I believe all the patches except 15/15 should be in a reasonable state
> for u-boot-testing.  I need to add an 'interrupt enable/disable' command
> but with a small hack I'm able to mimic the bootm command on ppc by:
> 
> 	boots start <A> <B> <C>

Per my previous comment: boots is already taken.

> 	boots load_os	/* hacked to disable interrupts */
> 	boots prep_os
> 	boots initrd_relocate
> 	boots fdt_relocate
> 	fdt chosen $initrd_start $initrd_end
> 	fdt boardsetup
> 	boots jump

Would "bootm go" be better than "bootm jump"?  I'm thinking we have a 
"go" command, so "bootm go" sounds better, more symmetric, to me.  Maybe 
I'm painting the bikeshed?

> Right now 15/15 is focused on only PPC w/Linux.  If this looks acceptable
> I'll split 15/15 into proper patches an add support for the other ARCHes
> and OSes.
> 
> - k

Thanks for working this,
gvb

  parent reply	other threads:[~2008-08-13  5:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 21:17 [U-Boot] [RFC][PATCH 00/15] bootm refactoring Kumar Gala
2008-08-12 21:17 ` [U-Boot] [RFC][PATCH 01/15] Update linux bootm to support ePAPR client interface Kumar Gala
2008-08-12 21:17   ` [U-Boot] [RFC][PATCH 02/15] add ability to disable ft_board_setup as part of bootm Kumar Gala
2008-08-12 21:17     ` [U-Boot] [RFC][PATCH 03/15] Clean up usage of icache_disable/dcache_disable Kumar Gala
2008-08-12 21:17       ` [U-Boot] [RFC][PATCH 04/15] fdt: added the ability to set initrd start/end via chosen command Kumar Gala
2008-08-12 21:17         ` [U-Boot] [RFC][PATCH 05/15] fdt: fdt addr w/o any args reports back the current working address Kumar Gala
2008-08-12 21:17           ` [U-Boot] [RFC][PATCH 06/15] bootm: refactor entry point code Kumar Gala
2008-08-12 21:17             ` [U-Boot] [RFC][PATCH 07/15] bootm: refactor ramdisk locating code Kumar Gala
2008-08-12 21:17               ` [U-Boot] [RFC][PATCH 08/15] bootm: refactor fdt locating and relocation code Kumar Gala
2008-08-12 21:17                 ` [U-Boot] [RFC][PATCH 09/15] bootm: Set working fdt address as part of the bootm flow Kumar Gala
2008-08-13  5:31 ` Jerry Van Baren [this message]
2008-08-13 12:43   ` [U-Boot] [RFC][PATCH 00/15] bootm refactoring Kumar Gala
2008-08-13 13:32     ` 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=48A271AF.6000508@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