OF /chosen/initrd,* variables - patch, official?
Hi guys,
Just a query here, there was a patch for /chosen/initrd,start and initrd,end variables gained from firmware or so, which allowed booting without getting those values into r3/r4, does anyone know the maintainer/author of that patch?
Also, what are the chances of pushing it for 2.6.23 or 2.6.24? I can imagine it's fairly useful (at least it is to me)..
Signature · 2 lines
Matt Sealey <[email protected]> Genesi, Manager, Developer Relations
Damn, I should use patchwork more efficiently;
http://patchwork.ozlabs.org/linuxppc/patch?q=initrd&filter=none&id=12168
Does anyone have any suggestion on the best way to integrate this so that it "just works" on OF platforms? It seems only to be usable way too late in boot to work, this code would have to be called in boot/main.c which seems relatively.. impossible to achieve.. or called in some specialised platform init code..
I hacked up a patch initially before I saw Milton's work and did it all in main.c (and did the same to mkvmlinuz..) and it seemed to work okay there.
I'm really curious as to the status and usefulness of this here.. :(
Signature · 2 lines
Matt Sealey <[email protected]> Genesi, Manager, Developer Relations
Quoted 10 lines · Matt Sealey
Hi guys,
Just a query here, there was a patch for /chosen/initrd,start and initrd,end variables gained from firmware or so, which allowed booting without getting those values into r3/r4, does anyone know the maintainer/author of that patch?
Also, what are the chances of pushing it for 2.6.23 or 2.6.24? I can imagine it's fairly useful (at least it is to me)..
Quoted 9 lines · Matt Sealey
Damn, I should use patchwork more efficiently;
http://patchwork.ozlabs.org/linuxppc/patch?q=initrd&filter=none&id=12168
Does anyone have any suggestion on the best way to integrate this so that it "just works" on OF platforms? It seems only to be usable way too late in boot to work, this code would have to be called in
boot/main.cwhich seems relatively.. impossible to achieve.. or called in some specialised platform init code..
It would have to be called from platform_init(). If called in main() it would clobber any other platform-specific initialization of the initrd parameters in loader_info.
Quoted 6 lines
I hacked up a patch initially before I saw Milton's work and did it all in
main.c(and did the same to mkvmlinuz..) and it seemed to work okay there.I'm really curious as to the status and usefulness of this here.. :(
Signature · 4 lines
David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Linux 2.6.23.rc3 boot issues on XUPV2P
Hi all.
I try to port Linux 2.6 on my XUPV2P Board which is based on ML300.
It runs sometimes, but for the usual case it just doesn't.
My problem is the initialization.
I have no clue why I get different values almost every time.
This is a log from the same zImage.elf, which is just loaded certain times in the row:
loaded at: 00400000 005331A0 board data at: 0000000E 0000008A relocated to: 00404084 00404100 zimage at: 00404EB9 00530A50 avail ram: 00534000 3B784800
Linux/PPC load: console=ttyS0,9600
Uncompressing Linux...done.
Now booting the kernel
loaded at: 00400000 005331A0 board data at: 00000000 0000007C relocated to: 00404084 00404100 zimage at: 00404EB9 00530A50 avail ram: 00534000 7C9E2378
Linux/PPC load: console=ttyS0,9600
Uncompressing Linux...done.
Now booting the kernel
loaded at: 00400000 005331A0 board data at: 40000000 4000007C relocated to: 00404084 00404100 zimage at: 00404EB9 00530A50 avail ram: 00534000 00000000
Linux/PPC load: console=ttyS0,9600
Uncompressing Linux...oops... out of memory
pause
loaded at: 00400000 005331A0 board data at: 00000001 0000007D relocated to: 00404084 00404100 zimage at: 00404EB9 00530A50 avail ram: 00534000 9E23787C
Linux/PPC load: console=ttyS0,9600
Uncompressing Linux...done.
Now booting the kernel
[ 0.000000] Linux version 2.6.23-rc3 (warkentin@iss2) (gcc version 4.1.1) #1 Tue Aug 21 14:01:45 CEST 2007 [ 0.000000] Xilinx ML300 Reference System (Virtex-II Pro) [ 0.000000] Zone PFN ranges: [ 0.000000] DMA 0 -> 196608
and just if the "avial ram" is about 10000000 it boots.
Anyone some idea why it could happens?
Quoted 11 lines · David Gibson
Quoted 9 lines · Matt Sealey
Damn, I should use patchwork more efficiently;
http://patchwork.ozlabs.org/linuxppc/patch?q=initrd&filter=none&id=12168
Does anyone have any suggestion on the best way to integrate this so that it "just works" on OF platforms? It seems only to be usable way too late in boot to work, this code would have to be called in
boot/main.cwhich seems relatively.. impossible to achieve.. or called in some specialised platform init code..
Quoted 3 lines
It would have to be called from
platform_init(). If called inmain()it would clobber any other platform-specific initialization of the initrd parameters inloader_info.
So just to get this straight.. platform_init would be the function called from md.init or would be better at md.setup_arch?
My goal right now is get something for CHRP (Pegasos) and Efika and try not to cause problems for anything else, but also really try not to clutter the thing with config checks, platform checks etc.
Signature · 2 lines
Matt Sealey <[email protected]> Genesi, Manager, Developer Relations
Quoted 12 lines · Matt Sealey
Quoted 11 lines · David Gibson
Quoted 9 lines · Matt Sealey
Damn, I should use patchwork more efficiently;
http://patchwork.ozlabs.org/linuxppc/patch?q=initrd&filter=none&id=12168
Does anyone have any suggestion on the best way to integrate this so that it "just works" on OF platforms? It seems only to be usable way too late in boot to work, this code would have to be called in
boot/main.cwhich seems relatively.. impossible to achieve.. or called in some specialised platform init code..
Quoted 6 lines
Quoted 3 lines
It would have to be called from
platform_init(). If called inmain()it would clobber any other platform-specific initialization of the initrd parameters inloader_info.So just to get this straight..
platform_initwould be the function called from md.init or would be better at md.setup_arch?
Uh... no... this is in the bootwrapper, long before ppc_md even exists. platform_init() is called from arch/powerpc/boot/crt0.S, immediately before main().
Quoted 4 lines
My goal right now is get something for CHRP (Pegasos) and Efika and try not to cause problems for anything else, but also really try not to clutter the thing with config checks, platform checks etc.
Signature · 4 lines
David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Re: Linux 2.6.23.rc3 boot issues on XUPV2P
In reply to Computer - ServiceQuoted 9 lines · Computer - Service
Hi all.
I try to port Linux 2.6 on my XUPV2P Board which is based on ML300.
It runs sometimes, but for the usual case it just doesn't. My problem is the initialization.
I have no clue why I get different values almost every time. This is a log from the same zImage.elf, which is just loaded certain times in the row:
Check that the Virtex support code in arch/ppc/boot/simple/embed_config.c is getting compiled in (hint:
search for ML403). If it's configured out, then your board info structure won't get setup correctly.
Cheers,
g.
Signature · 4 lines
Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. [email protected] (403) 399-0195
Quoted 3 lines · David Gibson
Uh... no... this is in the bootwrapper, long before
ppc_mdeven exists.platform_init()is called fromarch/powerpc/boot/crt0.S, immediately beforemain().
Oh *THAT* platform init.
So I could just drop a
} else {
dt_find_initrd();
}.. at the end and nobody would be too disgusted or have any problems?
Signature · 2 lines
Matt Sealey <[email protected]> Genesi, Manager, Developer Relations
Quoted 8 lines · Matt Sealey
Quoted 3 lines · David Gibson
Uh... no... this is in the bootwrapper, long before
ppc_mdeven exists.platform_init()is called fromarch/powerpc/boot/crt0.S, immediately beforemain().Oh *THAT* platform init.
Quoted 7 lines
So I could just drop a
} else { dt_find_initrd(); }.. at the end and nobody would be too disgusted or have any problems?
Err.. at the end of what? Each platform has it's own version of platform_init().
Signature · 4 lines
David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson
Quoted 9 lines · David Gibson
Quoted 8 lines · Matt Sealey
Quoted 3 lines · David Gibson
Uh... no... this is in the bootwrapper, long before
ppc_mdeven exists.platform_init()is called fromarch/powerpc/boot/crt0.S, immediately beforemain().Oh *THAT* platform init.
So I could just drop a
Quoted 8 lines
Quoted 5 lines
} else { dt_find_initrd(); }.. at the end and nobody would be too disgusted or have any problems?
Err.. at the end of what? Each platform has it's own version of
platform_init().
arch/powerpc/boot/of.c since it's not really relevant to me for non-OF platforms?
Signature · 2 lines
Matt Sealey <[email protected]> Genesi, Manager, Developer Relations
Quoted 14 lines · Matt Sealey
Quoted 13 lines · David Gibson
Quoted 12 lines · Matt Sealey
Quoted 3 lines · David Gibson
Uh... no... this is in the bootwrapper, long before
ppc_mdeven exists.platform_init()is called fromarch/powerpc/boot/crt0.S, immediately beforemain().Oh *THAT* platform init.
So I could just drop a
} else { dt_find_initrd(); }
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
.. at the end and nobody would be too disgusted or have any problems?
Err.. at the end of what? Each platform has it's own version of
platform_init().
arch/powerpc/boot/of.csince it's not really relevant to me for non-OF platforms?
Err... it would have to be a somewhat strange OF implementation that gives the linux,initrd-* properties sane values before entry... I doubt we want to do this for all real OF systems.
Signature · 4 lines
David Gibson | I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson