[RFC][PATCH] Put PReP boot arguments in a fixed location in the boot image

Tom Rini trini at kernel.crashing.org
Wed Mar 26 11:07:31 EST 2003

On Tue, Mar 25, 2003 at 08:01:32PM -0000, Leigh Brown wrote:
> Tom Rini said:
> > On Sat, Mar 22, 2003 at 08:31:18PM -0000, Leigh Brown wrote:
> >> I have been using this patch very successfully for ages.  Having the
> >> boot arguments in a fixed location in the boot image makes it trivial
> >> to write a program to set the arguments.
> >>
> >> Please take a look at the patch and let me know what you think.  If
> >> there are no negative comments I shall post it again for inclusion.
> >> The patch should apply against linuxppc_2_4 and linuxppc_2_4-devel.
> >
> > The changes to 'mkprep' I _think_ would break non-'PReP' systems using
> > that.  Please modify simple/head.S (and related) in a similar fashion,
> > and present this is a patch against 'linux-2.4' (GNU or BK patch is fine
> > with me).  Thanks.
> Hi Tom,
> Thanks for looking at the patch.  I hadn't realised that mkprep was used
> to build non-prep images (how silly of me ;-) ).  I looked at the simple/
> head.S and I'm a bit afraid to change it because I don't know anything
> about that code, and couldn't ever test it and so on.

All of the 'simple' code is based on 'prep'.  And the prep/ subdir will
die soon, as the needed changes to sanely 'hook' things into
decompress_kernel has gotten into Marcelo's tree.  What was prep/head.S
is simple/head.S and common/relocate.S.  Please give things a shot in
either a current linux-2.4 tree, or the linuxppc-2.4 tree (IIRC, it
should be rsync'able, if not, ping me off-list and I'll fix it).

Tom Rini

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

More information about the Linuxppc-dev mailing list