View Single Post
Posts: 2,154 | Thanked: 8,464 times | Joined on May 2010
#638
Originally Posted by Estel View Post
How? In orde to use diferent partition on eMMC, is it just matter of modifying:
Code:
ITEM_DEVICE="${EXT_CARD}p1"
...to contain INT_CARD and correct partition number?

This whole ITEM_DEVICE just tells u-boot on which partition to look for bootmenu.src file and bootmenu.img.d directory, yep? Or is it important for something else, too?
No, you can specify different path to first eMMC partition. Maemo using /home/user/MyDocs, but you can mount it to other path... now u-boot-update-bootmenu will work if you change it (by specifing path param).

ITEM_DEVICE will tell u-boot-update-bootmenu where to find kernel and initfs images. bootmenu.img.d must be always on first emmc partition.

Originally Posted by Estel View Post
If I want to have entry for booting uImage of certain name from SD card, as kernel for Maemo (no matter what kernel I actually put there, under that filename), do I still need to use those ITEM_INITRD and ITEM_CMDLINE, just because I'm using SD card? or is it required only for non-Maemo systems?
ITEM_INITRD tells u-boot what initrd file to use when booting. ITEM_CMDLINE overwrite default cmdline hardcoded in kernel image.

Originally Posted by Estel View Post
If yes, what is diferent on non-Maemo systems, that they need it? May it be, that in case of Maemo, ITEM_OMAPATAG make it read all those things from hardcoded place, and it is why we need to specify them manually, in case of non ITEM_OMAPATAG=1?
ITEM_OMAPATAG=1 will tell u-boot to add omap atag with n900 data into atag linked-list. omap atag is needed to boot some kernels (e.g maemo kernel)
 

The Following 4 Users Say Thank You to pali For This Useful Post: