1 |
Brenden Walker wrote: |
2 |
> I'm new to embedded linux, but been using Gentoo for a long time.. I'd like to use gentoo embedded of course. |
3 |
> |
4 |
> I'm working on a project that will likely be deployed on an ARM processor, the application will most likely be written in java so I need to be able to create a bootable ARM *nix image with a JVM installed on it. Our application would likely reside on writable media, the OS probably RO. |
5 |
> |
6 |
> I've setup a Gentoo system for cross dev to arm-unknown-linux-gnu and that all works. I've setup a seperate root and can emerge packages there. |
7 |
> |
8 |
> What I'm stumped on it how to make a bootable disk image. At this time the plan was to use QEMU to demonstrate the basic process and for use in developing our application, so a disk image suitable for QEMU is what I'm hoping for. |
9 |
> |
10 |
The concept of bootable disk doesn't really exist. On most ARM HW i've |
11 |
worked with the way the boot process works is you have a boot loader |
12 |
(redboot, uboot, etc) that loads the kernel, then the kernel paramaters |
13 |
tell it how to mount the root FS. |
14 |
|
15 |
QEMU works kinda the same. QEMU is the boot loader and you tell it the |
16 |
kernel image name, then pass the kernel args to mount the root for example: |
17 |
|
18 |
qemu-system-arm -M versatilepb -hda sda.img -kernel zImage -append |
19 |
"root=/dev/sda1 clock=pit" |
20 |
|
21 |
|
22 |
If your interested in the kernel details theres a general doc in |
23 |
<linux>/Documentation/arm/Booting |
24 |
|
25 |
|
26 |
I have an old (kernel 2.6.19) qemu image, based on one somebody on this |
27 |
list posted a long time ago, that you can boot: |
28 |
http://karl.hiramoto.org/embedded/qemu-arm.tar.lzma |
29 |
|
30 |
|
31 |
|
32 |
--karl |