Boot strategies and Boot Image formats in arch/powerpc

2006-07-21 Thread Claus Gindhart
Hi all,

currently i am trying to migrate our existing PowerPC board supports from the 
arch/ppc - directory into the new arch/powerpc. I am directly working within a 
cloned paulus_powerpc git repository on the most recent status.

We (Kontron) want to bring our kernel sources into the appropriate for an open 
source submission. We are modifying both our proprietary Bootloader, and the 
Linux Kernel, to make them fit to the new conventions, e.g. the flattened 
device tree.

However, i dont understand the following:

In the old structure, the kernel provided a bunch of sub directories 
(simple,openfirmware,...) to create a wrapper around the Linux kernel for 
brining it into the format, which is appropriate for the boot loader used.
This structure was easily adaptable for custom image formats.

Now, these dirs dont exist any more.

What is the strategy here (i could assume one the 3 variants below ?

a) Is it now in the responsibility of the bootloader, to support one of the 
image formats, 
which can be generated here currently ?

b) Will these subdirs (e.g. simple) come here, but just where not ported yet ?

c) Or, shall such wrapper around the kernel, and/or bringing the kernel into a 
particular file format
be performed outside the kernel source, by proprietary tools
(e.g. like U-boot does it with the mkimage tool) ?

-- 
Mit freundlichen Gruessen / Best regards

Claus Gindhart
SW RD
Kontron Modular Computers
phone :++49 (0)8341-803-374
mailto:claus.gindhart at kontron-modular.com
http://www.kontron.com

-BEGIN GEEK CODE BLOCK-
  Version: 3.1
  GU d- s++:++:+ a+ C++$ !U !P L++$ E-- W+(-) N- o?
  K? w !O !M V !PS PE- Y+ PGP+ t 5? X R* tv- b+ DI+++
  D-- G e++ h--- !r x+++
--END GEEK CODE BLOCK--






-- next part --
An HTML attachment was scrubbed...
URL: 
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060721/927c8511/attachment.htm
 


Boot strategies and Boot Image formats in arch/powerpc

2006-07-21 Thread Vitaly Bordug
On Fri, 21 Jul 2006 11:35:25 +0200
Claus Gindhart claus.gindhart at kontron.com wrote:

 Hi all,
 
 currently i am trying to migrate our existing PowerPC board supports from the 
 arch/ppc - directory into the new arch/powerpc. I am directly working within 
 a cloned paulus_powerpc git repository on the most recent status.
 
 We (Kontron) want to bring our kernel sources into the appropriate for an 
 open source submission. We are modifying both our proprietary Bootloader, and 
 the Linux Kernel, to make them fit to the new conventions, e.g. the flattened 
 device tree.
 
 However, i dont understand the following:
 
 In the old structure, the kernel provided a bunch of sub directories 
 (simple,openfirmware,...) to create a wrapper around the Linux kernel for 
 brining it into the format, which is appropriate for the boot loader used.
 This structure was easily adaptable for custom image formats.
 
 Now, these dirs dont exist any more.
Well, in arch/powerpc those stuff had no sense so far.. But it may change - see 
below.
 
 What is the strategy here (i could assume one the 3 variants below ?
 
 a) Is it now in the responsibility of the bootloader, to support one of the 
 image formats, 
 which can be generated here currently ?
 
This way we have started with powerpc merge and it still could be used. there 
are plenty of such stuff in the list archives, being discussed, and even 
followed up with patches.

But that imply u-boot firmware so not interesting for you I assume.

 b) Will these subdirs (e.g. simple) come here, but just where not ported 
 yet ?
 
Currently, Mark is working on a thing similar to this case. the kernel building 
zImage has to compile devicetree to binary dtb and line stuff up so that 
booting, the shim has started the kernel and have devicetree passed to it. 

 c) Or, shall such wrapper around the kernel, and/or bringing the kernel into 
 a particular file format
 be performed outside the kernel source, by proprietary tools
 (e.g. like U-boot does it with the mkimage tool) ?
 
This was yet another way pondered, but I guess b) looked better.

 -- 
 Mit freundlichen Gruessen / Best regards
 
 Claus Gindhart
 SW RD
 Kontron Modular Computers
 phone :++49 (0)8341-803-374
 mailto:claus.gindhart at kontron-modular.com
 http://www.kontron.com
 
 -BEGIN GEEK CODE BLOCK-
   Version: 3.1
   GU d- s++:++:+ a+ C++$ !U !P L++$ E-- W+(-) N- o?
   K? w !O !M V !PS PE- Y+ PGP+ t 5? X R* tv- b+ DI+++
   D-- G e++ h--- !r x+++
 --END GEEK CODE BLOCK--
 
 
 
 
 
 


-- 
Sincerely, 
Vitaly