[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#773255: Add TI OMAP5 uEVM board support db

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.


> +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?
      * Does it support loading from "sensible" (i.e. other than FAT and
        raw partitions) filesystems? (possibly via the generic load
      * Is /dev/mmcblk1p1 normally mounted (perhaps on /boot) or is it a
        dedicated boot partition which is not normally mounted?

Ultimately what I'm getting at is, can this platform use
bootscr.uboot-generic? I'd like to try and default to that wherever
possible for new platforms. (bootscr.omap predates all of the above
facilities being generally available in u-boot AFAIK).

On a separate note, there is no DTB-Id field. Does this mean that the
platform comes with a DTB in the firmware?


Reply to: