From Fedora Project Wiki
< Architectures | ARM
No edit summary |
|||
| Line 13: | Line 13: | ||
==== Boot Loader:==== | ==== Boot Loader:==== | ||
u-boot | u-boot | ||
==== Media:==== | |||
mmcblk | |||
==== Partition layout: ==== | ==== Partition layout: ==== | ||
| Line 35: | Line 38: | ||
==== Boot Loader:==== | ==== Boot Loader:==== | ||
u-boot | u-boot | ||
==== Media:==== | |||
mmcblk, sda | |||
==== Partition layout: ==== | ==== Partition layout: ==== | ||
| Line 47: | Line 53: | ||
==== Odities: ==== | ==== Odities: ==== | ||
sata disk is connected via usb to sata bridge | sata disk is connected via usb to sata bridge requiring "usb" bootloader commands | ||
| Line 54: | Line 60: | ||
==== Boot Loader:==== | ==== Boot Loader:==== | ||
==== Media:==== | |||
==== Partition layout: ==== | ==== Partition layout: ==== | ||
Revision as of 01:39, 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
Media:
mmcblk
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
Media:
mmcblk, sda
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 requiring "usb" bootloader commands