Originally Posted by Estel

Why so? using u-boot tools package, you can easily create u-boot with any attached kernel you like. Not to mention, that attaching kernels to u-boot is pointless - you can always boot from either eMMC or microSD stored kernel image, and this way you can forget flashing, when new KP comes out (only need to flash, when new u-boot appears). kernel is always loaded in RAM, anyway, so it's 0 difference if u-boot load it from NAND (attached), or from kernel image placed anywhere.

Except for fact, that with attached kernel, you need to flash them every time you want to have different one attached (usually, every new stable version of KP) - then it becomes almost equivalent of multiboot, re NAND war. So, attaching kernel is silly thing to do.

/Estel

Originally Posted by Estel

Why so? using u-boot tools package, you can easily create u-boot with any attached kernel you like. Not to mention, that attaching kernels to u-boot is pointless - you can always boot from either eMMC or microSD stored kernel image, and this way you can forget flashing, when new KP comes out (only need to flash, when new u-boot appears). kernel is always loaded in RAM, anyway, so it's 0 difference if u-boot load it from NAND (attached), or from kernel image placed anywhere.

Except for fact, that with attached kernel, you need to flash them every time you want to have different one attached (usually, every new stable version of KP) - then it becomes almost equivalent of multiboot, re NAND war. So, attaching kernel is silly thing to do.

/Estel

Originally Posted by pali

@Sohil876: Read first post, where is writen how to boot some entry as default (also when keyboard is closed).

Originally Posted by Sohil876

How can i do that with uboot tools? . side.

Originally Posted by pali

* u-boot-update-bootmenu can be configured to use different MyDocs, etc and boot paths (useful for non Maemo systems)

Originally Posted by pali

How to create bootmenu entry for U-Boot:
copy kernel image zImage-my to /opt/boot/
create config file in /etc/bootmenu.d/ with suffix .item

Bootmeny entry for other system on SD card:

Code:

ITEM_NAME="My name"
ITEM_KERNEL="uImage"
ITEM_INITRD="uInitrd"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext4"
ITEM_CMDLINE="kernel cmdline"

This means that you have SD card with first partition ext4. On that partition is kernel image with name uImage and initrd/initramfs file with name uInitrd (both generated by mkimage, see below

Originally Posted by Estel

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?

Originally Posted by Estel

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?

Originally Posted by Estel

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?

Originally Posted by panjgoori

finally I successfully migrated from multiboot to u-boot without messing with my device. But my phones bootmenu is different than the image attached at first post by pali.