> On Dec 19, 2014, at 10:54, Chen Baozi <baoz...@gmail.com> wrote: > >> >> On Dec 19, 2014, at 02:03, Ian Campbell <i...@debian.org> wrote: >> >> On Wed, 2014-12-17 at 23:28 +0800, Chen Baozi wrote: >>>> On Dec 17, 2014, at 23:04, Ian Campbell <i...@debian.org> wrote: >>>> >>>> On Wed, 2014-12-03 at 12:18 +0800, Chen Baozi wrote: >>>>> Package: flash-kernel >>>>> Version: 3.28 >>>>> Severity: wishlist >>>>> Tags: patch >>>>> >>>>> With the patch attached, TI OMAP5 uEVM board is supported. >>>> >>>> Thanks. >>>> >>>>> +Machine: TI OMAP5 uEVM board >>>>> +Method: generic >>>>> +U-Boot-Kernel-Address: 0x80008000 >>>>> +U-Boot-Initrd-Address: 0x0 >>>>> +U-Boot-Script-Address: 0x0 >>>>> +U-Boot-Script-Name: bootscr.omap >>>>> +Boot-Device: /dev/mmcblk1p1 >>>>> +Boot-Kernel-Path: uImage >>>>> +Boot-Initrd-Path: uInitrd >>>>> +Boot-Script-Path: boot.scr >>>>> +Required-Packages: u-boot-tools >>>> >>>> A few questions about u-boot on this platform: >>>> >>>> * Does it support the bootz command? >>> >>> The default one shipped with the board, which I got last year, seems not. >>> But I’m now using the latest upstream u-boot, which does support ‘bootz’.
I’ve only booted the system by ‘bootz’ without initrd. If I load the raw initrd image (rather than ‘uInitrd”), when I use bootz, it would output: Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid This is the reason that I’m still using bootm when initrd is needed. Baozi
signature.asc
Description: Message signed with OpenPGP using GPGMail