1. 24 Sep, 2014 1 commit
  2. 25 Aug, 2014 1 commit
  3. 20 Jun, 2014 1 commit
    • Simon Glass's avatar
      Add an I/O tracing feature · aa53233a
      Simon Glass authored
      When debugging drivers it is useful to see what I/O accesses were done
      and in what order.
      
      Even if the individual accesses are of little interest it can be useful to
      verify that the access pattern is consistent each time an operation is
      performed. In this case a checksum can be used to characterise the operation
      of a driver. The checksum can be compared across different runs of the
      operation to verify that the driver is working properly.
      
      In particular, when performing major refactoring of the driver, where the
      access pattern should not change, the checksum provides assurance that the
      refactoring work has not broken the driver.
      
      Add an I/O tracing feature and associated commands to provide this facility.
      It works by sneaking into the io.h heder for an architecture and redirecting
      I/O accesses through its tracing mechanism.
      
      For now no commands are provided to examine the trace buffer. The format is
      fairly simple, so 'md' is a reasonable substitute.
      
      Note: The checksum feature is only useful for I/O regions where the contents
      do not change outside of software control. Where this is not suitable you can
      fall back to manually comparing the addresses. It might be useful to enhance
      tracing to only checksum the accesses and not the data read/written.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      aa53233a
  4. 19 Jun, 2014 1 commit
    • Simon Glass's avatar
      bootm: Split out code from cmd_bootm.c · b6396403
      Simon Glass authored
      This file has code in three different categories:
      - Command processing
      - OS-specific boot code
      - Locating images and setting up to boot
      
      Only the first category really belongs in a file called cmd_bootm.c.
      
      Leave the command processing code where it is. Split out the OS-specific
      boot code into bootm_os.c. Split out the other code into bootm.c
      
      Header files and extern declarations are tidied but otherwise no code
      changes are made, to make it easier to review.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      b6396403
  5. 29 May, 2014 5 commits
  6. 08 May, 2014 2 commits
    • Sebastian Siewior's avatar
      usb/gadget: add the fastboot gadget · 3aab70af
      Sebastian Siewior authored
      This patch contains an implementation of the fastboot protocol on the
      device side and documentation. This is based on USB download gadget
      infrastructure. The fastboot function implements the getvar, reboot,
      download and reboot commands. What is missing is the flash handling i.e.
      writting the image to media.
      
      v3 (Rob Herring):
      This is based on http://patchwork.ozlabs.org/patch/126798/ with the
      following changes:
      - Rebase to current mainline and updates for current gadget API
      - Use SPDX identifiers for licenses
      - Traced the history and added missing copyright to cmd_fastboot.c
      - Use load_addr/load_size for transfer buffer
      - Allow vendor strings to be optional
      - Set vendor/product ID from config defines
      - Allow Ctrl-C to exit fastboot mode
      v4:
      - Major re-write to use the USB download gadget. Consolidated function
      code to a single file.
      - Moved globals into single struct.
      - Use puts and putc as appropriate.
      - Added CONFIG_USB_FASTBOOT_BUF_ADDR and CONFIG_USB_FASTBOOT_BUF_SIZE to
      set the fastboot transfer buffer.
      v5:
      - Add CONFIG option documentation to README
      - Rebase using new downloader registration
      Signed-off-by: default avatarSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
      3aab70af
    • Sebastian Siewior's avatar
      image: add support for Android's boot image format · 9ace3fc8
      Sebastian Siewior authored
      This patch adds support for the Android boot-image format. The header
      file is from the Android project and got slightly alterted so the struct +
      its defines are not generic but have something like a namespace. The
      header file is from bootloader/legacy/include/boot/bootimg.h. The header
      parsing has been written from scratch and I looked at
      bootloader/legacy/usbloader/usbloader.c for some details.
      The image contains the physical address (load address) of the kernel and
      ramdisk. This address is considered only for the kernel image.
      The "second image" defined in the image header is currently not
      supported. I haven't found anything that is creating this.
      
      v3 (Rob Herring):
      This is based on http://patchwork.ozlabs.org/patch/126797/ with the
      following changes:
      - Rebased to current mainline
      - Moved android image handling to separate functions in
        common/image-android.c
      - s/u8/char/ in header to fix string function warnings
      - Use SPDX identifiers for licenses
      - Cleaned-up file source information:
        android_image.h is from file include/boot/bootimg.h in repository:
        https://android.googlesource.com/platform/bootable/bootloader/legacy
        The git commit hash is 4205b865141ff2e255fe1d3bd16de18e217ef06a
        usbloader.c would be from the same commit, but it does not appear
        to have been used for any actual code.
      v4:
      - s/andriod/android/
      - Use a separate flag ep_found to track if the entry point has been set
      rather than using a magic value.
      
      Cc: Wolfgang Denk <wd@denx.de>
      Signed-off-by: default avatarSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
      Reviewed-by: default avatarTom Rini <trini@ti.com>
      Reviewed-by: default avatarLukasz Majewski <l.majewski@samsung.com>
      9ace3fc8
  7. 22 Mar, 2014 1 commit
  8. 21 Mar, 2014 1 commit
  9. 18 Mar, 2014 1 commit
  10. 04 Mar, 2014 1 commit
  11. 26 Feb, 2014 1 commit
    • Tom Rini's avatar
      arm: Switch to -mno-unaligned-access when supported by the compiler · 1551df35
      Tom Rini authored
      When we tell the compiler to optimize for ARMv7 (and ARMv6 for that
      matter) it assumes a default of SCTRL.A being cleared and unaligned
      accesses being allowed and fast at the hardware level.  We set this bit
      and must pass along -mno-unaligned-access so that the compiler will
      still breakdown accesses and not trigger a data abort.
      
      To better help understand the requirements of the project with respect
      to unaligned memory access, the
      Documentation/unaligned-memory-access.txt file has been added as
      doc/README.unaligned-memory-access.txt and is taken from the v3.14-rc1
      tag of the kernel.
      
      Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
      Cc: Mans Rullgard <mans@mansr.com>
      Signed-off-by: default avatarTom Rini <trini@ti.com>
      1551df35
  12. 21 Feb, 2014 1 commit
  13. 19 Feb, 2014 3 commits
    • Masahiro Yamada's avatar
      kbuild: use Linux Kernel build scripts · 6825a95b
      Masahiro Yamada authored
      Now we are ready to switch over to real Kbuild.
      
      This commit disables temporary scripts:
        scripts/{Makefile.build.tmp, Makefile.host.tmp}
      and enables real Kbuild scripts:
        scripts/{Makefile.build,Makefile.host,Makefile.lib}.
      
      This switch is triggered by the line in scripts/Kbuild.include
        -build := -f $(if $(KBUILD_SRC),$(srctree)/)scripts/Makefile.build.tmp obj
        +build := -f $(if $(KBUILD_SRC),$(srctree)/)scripts/Makefile.build obj
      
      We need to adjust some build scripts for U-Boot.
      But smaller amount of modification is preferable.
      
      Additionally, we need to fix compiler flags which are
      locally added or removed.
      
      In Kbuild, it is not allowed to change CFLAGS locally.
      Instead, ccflags-y, asflags-y, cppflags-y,
      CFLAGS_$(basetarget).o, CFLAGS_REMOVE_$(basetarget).o
      are prepared for that purpose.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Tested-by: default avatarGerhard Sittig <gsi@denx.de>
      6825a95b
    • Masahiro Yamada's avatar
      kbuild: change out-of-tree build · 9e414032
      Masahiro Yamada authored
      This commit changes the working directory
      where the build process occurs.
      
      Before this commit, build process occurred under the source
      tree for both in-tree and out-of-tree build.
      
      That's why we needed to add $(obj) prefix to all generated
      files in makefiles like follows:
        $(obj)u-boot.bin:  $(obj)u-boot
      
      Here, $(obj) is empty for in-tree build, whereas it points
      to the output directory for out-of-tree build.
      
      And our old build system changes the current working directory
      with "make -C <sub-dir>" syntax when descending into the
      sub-directories.
      
      On the other hand, Kbuild uses a different idea
      to handle out-of-tree build and directory descending.
      
      The build process of Kbuild always occurs under the output tree.
      When "O=dir/to/store/output/files" is given, the build system
      changes the current working directory to that directory and
      restarts the make.
      
      Kbuild uses "make -f $(srctree)/scripts/Makefile.build obj=<sub-dir>"
      syntax for descending into sub-directories.
      (We can write it like "make $(obj)=<sub-dir>" with a shorthand.)
      This means the current working directory is always the top
      of the output directory.
      Signed-off-by: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Tested-by: default avatarGerhard Sittig <gsi@denx.de>
      9e414032
    • Dan Murphy's avatar
      common: spl: Add spl sata boot support · fff40a7e
      Dan Murphy authored
      Add spl_sata to read a fat partition from a bootable SATA
      drive.
      Signed-off-by: default avatarDan Murphy <dmurphy@ti.com>
      Reviewed-by: default avatarRoger Quadros <rogerq@ti.com>
      fff40a7e
  14. 04 Feb, 2014 1 commit
  15. 24 Jan, 2014 1 commit
  16. 13 Dec, 2013 1 commit
  17. 25 Nov, 2013 1 commit
  18. 31 Oct, 2013 1 commit
  19. 20 Oct, 2013 1 commit
  20. 25 Jul, 2013 1 commit
  21. 24 Jul, 2013 1 commit
  22. 01 Jul, 2013 1 commit
  23. 26 Jun, 2013 2 commits
  24. 20 Jun, 2013 2 commits
  25. 14 May, 2013 2 commits
  26. 13 May, 2013 1 commit
  27. 28 Apr, 2013 1 commit
  28. 11 Apr, 2013 1 commit
  29. 29 Mar, 2013 1 commit
    • Pali Rohár's avatar
      New command bootmenu: ANSI terminal boot menu support · e7abe919
      Pali Rohár authored
      The "bootmenu" command uses U-Boot menu interfaces and provides
      a simple mechanism for creating menus with several boot items.
      When running this command the menu will be assembled as defined
      by a set of environment variables which contain a title and
      command key-value pairs. The "Up" and "Down" keys are used for
      navigation through the items. Current active menu item is
      highlighted and can be selected using the "Enter" key.
      
      The command interprets and generates various ANSI escape
      sequencies, so for proper menu rendering and item selection
      the used terminal should support them.
      Signed-off-by: default avatarPali Rohár <pali.rohar@gmail.com>
      [agust: various fixes and documentation updates]
      Signed-off-by: default avatarAnatolij Gustschin <agust@denx.de>
      e7abe919
  30. 18 Mar, 2013 1 commit