Skip to content

U
U-Boot.Mirror

OS / U-Boot.Mirror

通知 1
Star 0
Fork 0
U
U-Boot.Mirror

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 04 6月, 2016 1 次提交
    • M
      usb: move CONFIG_USB_XHCI to Kconfig with renaming · 0a8cc1a3
      由 Masahiro Yamada 提交于 
      Move CONFIG_USB_XHCI to defconfig files for all boards, renaming it
into CONFIG_USB_XHCI_HCD.

As commented in the help of "config USB_XHCI" entry, this has been
a TODO for a long time; now CONFIG_USB_XHCI_HCD and CONFIG_USB_XHCI
have been unified in favor of the former.

Note:
Some boards define CONFIG_USB_XHCI in their headers without
CONFIG_USB, which does not meet the "depends on" in Kconfig.
I added CONFIG_USB=y for those boards when converting.
Otherwise, they would fail to build.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      0a8cc1a3
  3. 28 5月, 2016 3 次提交
    • M
      ti: AM43xx: Use CONFIG options from SOC Kconfig · 9aac7d0e
      由 Madan Srinivas 提交于 
      Updates configs/am43xx_evm.h to use CONFIG options from
SOC specific Kconfig file for various calculations.

On AM43x devices, the address of SPL entry point  depends on
the device type, i.e. whether it is secure or non-secure.

Further, for non-secure devices, the SPL entry point is different
between  USB HOST boot mode, other "memory" boot modes (MMC, NAND)
and "peripheral" boot modes (UART, USB)

To add to the complexity, on secure devices, in addition to the
above differences, the SPL entry point can change because of the
space occupied by other components (other than u-boot or spl)
that go into a secure boot image.

To prevent the user from having to modify source files every time
any component of the secure image changes, the value of
CONFIG_SPL_TEXT_BASE has been set using a Kconfig option that
is supplied in the am43xx_*_defconfig files

Using the CONFIG options also enables us to do away with some
compile time flags that were used to specify CONFIG_SPL_TEXT_BASE
for different boot modes.

On QSPI devices, the same problem described above occurs w.r.t. the
address of the u-boot entry point in flash, when booting secure
devices. To handle this, CONFIG_SYS_TEXT_BASE is also setup via
a Kconfig option and the defconfig files.
Signed-off-by: NMadan Srinivas <madans@ti.com>
Signed-off-by: NDaniel Allred <d-allred@ti.com>
Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
Tested-by: NAndreas Dannenberg <dannenberg@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>
      9aac7d0e
    • M
      arm: Kconfig: Add support for AM43xx SoC specific Kconfig · 6384726d
      由 Madan Srinivas 提交于 
      Adding support for AM43xx secure devices require the addition
of some SOC specific config options like the amount of memory
used by public ROM and the address of the entry point of u-boot
or SPL, as seen by the ROM code, for the image to be built
correctly.

This mandates the addition of am AM43xx CONFIG option and the
ARM Kconfig file has been modified to source this SOC Kconfig
file. Moving the TARGET_AM43XX_EVM config option to the SOC
KConfig and out of the arch/arm/Kconfig.

Updating defconfigs to add the CONFIG_AM43XX=y statement and
removing the #define CONFIG_AM43XX from the header file.
Signed-off-by: NMadan Srinivas <madans@ti.com>
Signed-off-by: NDaniel Allred <d-allred@ti.com>
Tested-by: NAndreas Dannenberg <dannenberg@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>
      6384726d
    • A
      net: Move CONFIG_SPL_NET_VCI_STRING into Kconfig · 210be5c4
      由 Alexander Graf 提交于 
      This patch also adds the SPL time VCI string into Kconfig.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Reviewed-by: NTom Rini <trini@konsulko.com>
      210be5c4
  5. 26 4月, 2016 3 次提交
  7. 20 4月, 2016 6 次提交
  9. 26 3月, 2016 1 次提交
  11. 15 3月, 2016 1 次提交
  13. 25 11月, 2015 2 次提交
  15. 22 11月, 2015 1 次提交
  17. 19 11月, 2015 1 次提交
  19. 26 6月, 2015 2 次提交
  21. 01 6月, 2015 1 次提交
  23. 13 5月, 2015 1 次提交
  25. 30 7月, 2014 1 次提交
    • M
      kconfig: add board Kconfig and defconfig files · dd84058d
      由 Masahiro Yamada 提交于 
      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: NMasahiro Yamada <yamada.m@jp.panasonic.com>
Acked-by: NSimon Glass <sjg@chromium.org>
      dd84058d