No edit summary |
|||
Line 18: | Line 18: | ||
==== File systems: ==== | ==== File systems: ==== | ||
/boot/uboot needs to be vfat, /boot needs to be ext2 or ext3, / can be | /boot/uboot needs to be partition #1 and vfat with specific sector boundaries, /boot needs to be ext2 or ext3, / can be | ||
==== Special Packages: ==== | ==== Special Packages: ==== |
Revision as of 01:36, 26 April 2013
About
The idea behind this page is to describe the parameters for all the ARM systems we intend to support.
Systems
OMAP
Install Mechanism:
disk image
Boot Loader:
u-boot
Partition layout:
/boot/uboot /boot / msdos labels
File systems:
/boot/uboot needs to be partition #1 and vfat with specific sector boundaries, /boot needs to be ext2 or ext3, / can be
Special Packages:
uboot-panda uboot-beagle uboot-beaglebone
DTB Files:
Odities:
MLO file needs to be first thing copied to the vfat partition, then a uboot.img and a uEnv.txt file written. It is anticipated that a deoployment tool will populate /boot/uboot for the target-board
Trimslice
Install Mechanism:
anaconda sdcard
Boot Loader:
u-boot
Partition layout:
/boot /
File systems:
/boot needs to be ext2 or ext3
Special Packages:
DTB Files:
Odities:
sata disk is connected via usb to sata bridge