12 Oct, 2016

1 commit


10 Sep, 2016

1 commit

  • We only need the function found in cmd/disk.c when we have IDE, SCSI or
    USB_STORAGE enabled. While the first two are easy to get right, in the
    3rd case we assume that the set of cases where we do have USB and do not
    enable USB_STORAGE are small enough that we can take the small bloat of
    un-discarded strings on gcc prior to 6.x

    Signed-off-by: Tom Rini

    Tom Rini
     

20 Aug, 2016

1 commit

  • The bootz and booti commands rely on common functionality that is found
    in common/bootm.c and common/bootm_os.c. They do not however rely on
    the rest of cmd/bootm.c to be implemented so split them into their own
    files. Have various Makefiles include the required infrastructure for
    CONFIG_CMD_BOOT[IZ] as well as CONFIG_CMD_BOOTM. Move the declaration
    of 'images' over to common/bootm.c.

    Cc: Masahiro Yamada
    Signed-off-by: Tom Rini

    Tom Rini
     

25 Jun, 2016

1 commit


23 May, 2016

3 commits


17 May, 2016

2 commits

  • At present the SCSI command code includes both the command-processing code
    and the core SCSI functions and data structures.

    Separate the latter into its own file, adding functions as needed to avoid
    the command code accessing data structures directly. This functions use the
    new legacy block functions.

    With this commit:
    - There is no CONFIG option referenced from the command code
    - The concept of a 'current SCSI device' is confined to the command code

    This will make it easier to convert this code to driver model.

    Signed-off-by: Simon Glass

    Simon Glass
     
  • This option currently enables both the command and the SCSI functionality.
    Rename the existing option to CONFIG_SCSI since most of the code relates
    to the feature.

    Signed-off-by: Simon Glass

    Simon Glass
     

19 Apr, 2016

1 commit


02 Apr, 2016

1 commit

  • Add a block device cache to speed up repeated reads of block devices by
    various filesystems.

    This small amount of cache can dramatically speed up filesystem
    operations by skipping repeated reads of common areas of a block
    device (typically directory structures).

    This has shown to have some benefit on FAT filesystem operations of
    loading a kernel and RAM disk, but more dramatic benefits on ext4
    filesystems when the kernel and/or RAM disk are spread across
    multiple extent header structures as described in commit fc0fc50.

    The cache is implemented through a minimal list (block_cache) maintained
    in most-recently-used order and count of the current number of entries
    (cache_count). It uses a maximum block count setting to prevent copies
    of large block reads and an upper bound on the number of cached areas.

    The maximum number of entries in the cache defaults to 32 and the maximum
    number of blocks per cache entry has a default of 2, which has shown to
    produce the best results on testing of ext4 and FAT filesystems.

    The 'blkcache' command (enabled through CONFIG_CMD_BLOCK_CACHE) allows
    changing these values and can be used to tune for a particular filesystem
    layout.

    Signed-off-by: Eric Nelson

    Eric Nelson
     

16 Mar, 2016

1 commit

  • In order to execute an EFI application, we need to bridge the gap between
    U-Boot's notion of executing images and EFI's notion of doing the same.

    The best path forward IMHO here is to stick completely to the way U-Boot
    deals with payloads. You manually load them using whatever method to RAM
    and then have a simple boot command to execute them. So in our case, you
    would do

    # load mmc 0:1 $loadaddr grub.efi
    # bootefi $loadaddr

    which then gets you into a grub shell. Fdt information known to U-boot
    via the fdt addr command is also passed to the EFI payload.

    Signed-off-by: Alexander Graf
    Reviewed-by: Simon Glass
    Tested-by: Simon Glass
    [trini: Guard help text with CONFIG_SYS_LONGHELP]
    Signed-off-by: Tom Rini

    Alexander Graf
     

25 Jan, 2016

2 commits

  • Now that they are in their own directory, we can remove this prefix.
    This makes it easier to find a file since the prefix does not get in the
    way.

    Signed-off-by: Simon Glass
    Reviewed-by: Bin Meng
    Reviewed-by: Heiko Schocher
    Acked-by: Stefan Roese
    Acked-by: Przemyslaw Marczak

    Simon Glass
     
  • There are a lot of unrelated files in common, including all of the commands.
    Moving them into their own directory makes them easier to find and is more
    logical.

    Some commands include non-command code, such as cmd_scsi.c. This should be
    sorted out at some point so that the function can be enabled with or without
    the associated command.

    Unfortunately, with m68k I get this error:

    m68k: + M5329AFEE
    +arch/m68k/cpu/mcf532x/start.o: In function `_start':
    +arch/m68k/cpu/mcf532x/start.S:159:(.text+0x452): relocation truncated to fit: R_68K_PC16 against symbol `board_init_f' defined in .text.board_init_f section in common/built-in.o

    I hope someone can shed some light on what this means. I hope it isn't
    depending on the position of code in the image.

    Signed-off-by: Simon Glass
    Reviewed-by: Bin Meng
    Reviewed-by: Heiko Schocher
    Acked-by: Stefan Roese
    Acked-by: Przemyslaw Marczak

    Simon Glass