1. 10 Dec, 2015 1 commit
  2. 22 Nov, 2015 1 commit
  3. 18 Nov, 2015 1 commit
  4. 20 Oct, 2015 1 commit
  5. 31 Aug, 2015 1 commit
  6. 25 Jul, 2015 1 commit
  7. 26 Jun, 2015 2 commits
  8. 05 Jun, 2015 1 commit
  9. 01 Jun, 2015 2 commits
  10. 12 May, 2015 1 commit
  11. 04 May, 2015 1 commit
  12. 15 Mar, 2015 1 commit
  13. 22 Jan, 2015 2 commits
    • Hans de Goede's avatar
      sunxi: Remove CONFIG_TARGET_FOO for sun4i, sun6i and sun8i boards · 69152708
      Hans de Goede authored
      CONFIG_TARGET_FOO is only used in board/sunxi/Makefile to select the
      dram config for sun5i and sun7i boards and in board/sunxi/gmac.c for some
      special handling of the bananapi/bananapro (both sun7i), iow it is not used
      at all on any sun4i, sun6i and sun8i boards so lets get rid of it there.
      Signed-off-by: 's avatarHans de Goede <hdegoede@redhat.com>
      Acked-by: 's avatarIan Campbell <ijc@hellion.org.uk>
    • Hans de Goede's avatar
      sunxi: Stop differentiating between 512M and 1G variants of the same board · 8ffc487c
      Hans de Goede authored
      While working on adding more boards I noticed that we lack a config for
      the 512M cubieboard, and that some of the new boards which I want to add also
      have 512M and 1G variants, rather then adding 2 defconfig's for all of these,
      lets switch the exising boards which have both a 512M and 1024M variant over
      to the sun4i dram autoconfig code.
      This also drops the foo_RAMSIZE_defconfig variants of boards where we currently
      have 2 separate configs already.
      1) The newly introduced CONFIG_DRAM_EMR1 kconfig value is not used with
      a value other then its default for now, but we need this to be configurable
      to support some new boards with auto dram config.
      2) We always set all CONFIG_DRAM_foo values in defconfigs, even if they match
      the defaults, this is done to make it more clear what values are used for a
      certain board.
      This has been tested on a Mele A1000, Mini-X and a Cubieboard, all 1G
      variants, the dram autoconfig code has also been tested on a 512M mk802
      (a defconfig for the mk802 is added in a later patch).
      Signed-off-by: 's avatarHans de Goede <hdegoede@redhat.com>
      Acked-by: 's avatarIan Campbell <ijc@hellion.org.uk>
  14. 05 Nov, 2014 3 commits
    • Ian Campbell's avatar
      sunxi: kconfig: Introduce CONFIG_TARGET_<BOARD> · d9a20476
      Ian Campbell authored
      This was done automatically with the following bits of scripting.
      The Kconfig choice content was generated with this script snippet:
          for i in $(git grep -l CONFIG_ARCH_SUNXI configs/*) ; do
              TARGET=$(sed -n -e 's/CONFIG_SYS_EXTRA_OPTIONS="\([^,"]\+\).*/\1/p' $i);
              MACH=$(sed -n -e 's/.*CONFIG_\(MACH_SUN.I\)=./\1/p' $i)
              echo "config TARGET_$TARGET"
              echo "	bool \"$TARGET\""
              echo "	depends on $MACH"
      defconfigs were updated with a sed script (t):
          # Extract board from first entry of CONFIG_SYS_EXTRA_OPTIONS,
              # Print and delete first line (CONFIG_SYS_EXTRA_OPTIONS), leaving
              # CONFIG_TARGET_<BOARD> in pattern space
          # Move CONFIG_TARGET_<BOARD> to hold space
          # Print CONFIG_TARGET_<BOARD> after CONFIG_MACH_<SOC> in either SPL or
          # normal mode.
          # Print any remaining lines normally
      Run as:
          sed -i -n -f t $(git grep -l CONFIG_ARCH_SUNXI configs/*)
      and then manually removing the one instance of CONFIG_SYS_EXTRA_OPTIONS="" from
      board/sunxi/Makefile was updated with:
          sed -e 's/^\(obj-\$(CONFIG_\)\(.*\)\().*+= dram_.*\)/\1TARGET_\2\3/g' board/sunxi/Makefile
      and manually retabbing a few lines to line up again.
      The board descriptions could certainly be improved.
      Signed-off-by: 's avatarIan Campbell <ijc@hellion.org.uk>
      Reviewed-by: 's avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: 's avatarHans de Goede <hdegoede@redhat.com>
    • Ian Campbell's avatar
      sunxi: kconfig: Rename TARGET_SUN[45678]I to MACH_SUN[45678]I. · c3be2793
      Ian Campbell authored
      Now we have CONFIG_ARCH_SUNXI as the toplevel, CONFIG_MACH_SUN[45678]I as the
      per-SoC option and leave CONFIG_TARGET_BLAH free for individual boards in the
      Done automatically with:
          sed -i -e 's/TARGET_\(SUN[45678]I\)/MACH_\1/g' $(git grep -l TARGET_SUN[45678]I)
      Signed-off-by: 's avatarIan Campbell <ijc@hellion.org.uk>
      Reviewed-by: 's avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: 's avatarHans de Goede <hdegoede@redhat.com>
    • Ian Campbell's avatar
      sunxi: kconfig: Add top-level ARCH_SUNXI · 2c7e3b90
      Ian Campbell authored
      And make TARGET_SUN[45678]I a choice variable under this.
      configs updated with:
          sed -i -e 's/^\(\+S:\)\?CONFIG_TARGET_SUN.I=y/\1CONFIG_ARCH_SUNXI=y\n&/g' configs/*
      Signed-off-by: 's avatarIan Campbell <ijc@hellion.org.uk>
      Reviewed-by: 's avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: 's avatarHans de Goede <hdegoede@redhat.com>
  15. 05 Sep, 2014 2 commits
  16. 12 Aug, 2014 1 commit
  17. 31 Jul, 2014 2 commits
  18. 30 Jul, 2014 1 commit
    • Masahiro Yamada's avatar
      kconfig: add board Kconfig and defconfig files · dd84058d
      Masahiro Yamada authored
      This commit adds:
       - arch/${ARCH}/Kconfig
          provide a menu to select target boards
       - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
          set CONFIG macros to the appropriate values for each board
       - configs/${TARGET_BOARD}_defconfig
          default setting of each board
      (This commit was automatically generated by a conversion script
      based on boards.cfg)
      In Linux Kernel, defconfig files are located under
      arch/${ARCH}/configs/ directory.
      It works in Linux Kernel since ARCH is always given from the
      command line for cross compile.
      But in U-Boot, ARCH is not given from the command line.
      Which means we cannot know ARCH until the board configuration is done.
      That is why all the "*_defconfig" files should be gathered into a
      single directory ./configs/.
      Signed-off-by: 's avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: 's avatarSimon Glass <sjg@chromium.org>