1 | # |
---|
2 | # $Id$ |
---|
3 | # |
---|
4 | |
---|
5 | The code in this directory has been taken WITH PERMISSION from |
---|
6 | Gabriel Paubert, paubert@iram.es. The main reason for having |
---|
7 | a separate bootloader for PreP compliant firmware is that the |
---|
8 | initial code is relocated by firmware at an unknow address |
---|
9 | (actually 0x5000 on motorola MCP750) and that as Gabriel I |
---|
10 | think having a relocatable bootloder code is a must. |
---|
11 | |
---|
12 | So the way of building a binary executable that can be booted via |
---|
13 | hard disk or network boot goes like this : |
---|
14 | |
---|
15 | - make a RTEMS executable, |
---|
16 | - put is as data section in the bootloder binary, |
---|
17 | - relink the loader (see make-exe macros for details), |
---|
18 | |
---|
19 | I would like to thank Gabriel for his support and his code. |
---|
20 | The original code can be found in form of a patch to official linux |
---|
21 | kernel at (I insist not vger ppc kernel or Imac ppc kernels!!) : |
---|
22 | |
---|
23 | <ftp://vlab1.iram.es/pub/linux-2.2/> |
---|
24 | |
---|
25 | After applying the patch, the code is located in a new directory |
---|
26 | called prepboot. |
---|
27 | |
---|
28 | (NB : note use ftp not netscape...) |
---|
29 | |
---|
30 | Note that the actual code differs a lot since Gabriel choose to use |
---|
31 | a CHRP compliant mapping instead of a Prep Mapping to save |
---|
32 | BATs. I had no time to upgrade the code to its new one allthough |
---|
33 | I agree it should be done... |
---|
34 | |
---|
35 | I have also splitted the original code to have a more modular |
---|
36 | design enabling to reuse code between the loader and RTEMS |
---|
37 | initialization (e.g printk, ...). |
---|
38 | |
---|
39 | Eric Valette (valette@crf.canon.fr) |
---|
40 | |
---|
41 | |
---|