1. 15 Jul, 2016 1 commit
    • Simon Glass's avatar
      sandbox: Add a new sandbox_spl board · 8797b2ca
      Simon Glass authored
      It is useful to be able to build SPL for sandbox. It provides additional
      build coverage and allows SPL features to be tested in sandbox. However
      it does not need worthwhile to always create an SPL build. It nearly
      doubles the build time and the feature is (so far) seldom used.
      
      So for now, create a separate build target for sandbox SPL. This allows
      experimentation with this new feature without impacting existing workflows.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      8797b2ca
  2. 18 Apr, 2016 1 commit
  3. 20 Nov, 2015 1 commit
  4. 21 May, 2015 1 commit
  5. 18 Apr, 2015 4 commits
    • Masahiro Yamada's avatar
      dm: select CONFIG_DM* options · 58d423b8
      Masahiro Yamada authored
      As mentioned in the previous commit, adding default values in each
      Kconfig causes problems because it does not co-exist with the
      "depends on" syntax.  (Please note this is not a bug of Kconfig.)
      We should not do so unless we have a special reason.  Actually,
      for CONFIG_DM*, we have no good reason to do so.
      
      Generally, CONFIG_DM is not a user-configurable option.  Once we
      convert a driver into Driver Model, the board only works with Driver
      Model, i.e. CONFIG_DM must be always enabled for that board.
      So, using "select DM" is more suitable rather than allowing users to
      modify it.  Another good thing is, Kconfig warns unmet dependencies
      for "select" syntax, so we easily notice bugs.
      
      Actually, CONFIG_DM and other related options have been added
      without consistency: some into arch/*/Kconfig, some into
      board/*/Kconfig, and some into configs/*_defconfig.
      
      This commit prefers "select" and cleans up the following issues.
      
      [1] Never use "CONFIG_DM=n" in defconfig files
      
      It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
      It is more common to use "# CONFIG_FOO is not set".  But here, we
      do not even have to do it.
      Less than half of OMAP3 boards have been converted to Driver Model.
      Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
      weird.  Instead, add "select DM" only to appropriate boards, which
      eventually eliminates "CONFIG_DM=n", etc.
      
      [2] Delete redundant CONFIGs
      
      Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
      in configs/sandbox_defconfig.
      Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
      defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      58d423b8
    • Simon Glass's avatar
      cros_ec: Drop unused CONFIG_DM_CROS_EC · 60f37fc6
      Simon Glass authored
      Since all supported boards enable this option now, we can remove it along
      with the old code.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      60f37fc6
    • Joe Hershberger's avatar
      sandbox: eth: Add a bridge to a real network for sandbox · a346ca79
      Joe Hershberger authored
      Implement a bridge between U-Boot's network stack and Linux's raw packet
      API allowing the sandbox to send and receive packets using the host
      machine's network interface.
      
      This raw Ethernet API requires elevated privileges.  You can either run
      as root, or you can add the capability needed like so:
      
      sudo /sbin/setcap "CAP_NET_RAW+ep" /path/to/u-boot
      Signed-off-by: default avatarJoe Hershberger <joe.hershberger@ni.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      a346ca79
    • Joe Hershberger's avatar
      sandbox: eth: Add network support to sandbox · 3ea143ab
      Joe Hershberger authored
      Add basic network support to sandbox which includes a network driver.
      Signed-off-by: default avatarJoe Hershberger <joe.hershberger@ni.com>
      Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
      3ea143ab
  6. 17 Apr, 2015 1 commit
  7. 12 Feb, 2015 1 commit
  8. 13 Sep, 2014 1 commit
  9. 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: default avatarMasahiro Yamada <yamada.m@jp.panasonic.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      dd84058d