Eric Lee / smarc-uboot

15 Dec, 2019

1 commit

  • b31129528   x86: Add an option to control the position of U-Boot ... Browse Code »

    The existing work-around for positioning U-Boot in the ROM when it
    actually runs from RAM still exists and there is not obvious way to change
    this.

    Add a proper Kconfig option to handle this case. This also adds a new bool
    property to indicate whether CONFIG_SYS_TEXT_BASE exists.

    Signed-off-by: Simon Glass
    Reviewed-by: Bin Meng

    Simon Glass
     

05 Dec, 2019

1 commit

21 Nov, 2019

2 commits

  • a09fea1d2   env: Finish migration of common ENV options ... Browse Code »
    1

    - In ARMv8 NXP Layerscape platforms we also need to make use of
    CONFIG_SYS_RELOC_GD_ENV_ADDR now, do so.
    - On ENV_IS_IN_REMOTE, CONFIG_ENV_OFFSET is never used, drop the define
    to 0.
    - Add Kconfig entry for ENV_ADDR.
    - Make ENV_ADDR / ENV_OFFSET depend on the env locations that use it.
    - Add ENV_xxx_REDUND options that depend on their primary option and
    SYS_REDUNDAND_ENVIRONMENT
    - On a number of PowerPC platforms, use SPL_ENV_ADDR not CONFIG_ENV_ADDR
    for the pre-main-U-Boot environment location.
    - On ENV_IS_IN_SPI_FLASH, check not for CONFIG_ENV_ADDR being set but
    rather it being non-zero, as it will now be zero by default.
    - Rework the env_offset absolute in env/embedded.o to not use
    CONFIG_ENV_OFFSET as it was the only use of ENV_OFFSET within
    ENV_IS_IN_FLASH.
    - Migrate all platforms.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Cc: Patrick Delaunay
    Cc: uboot-stm32@st-md-mailman.stormreply.com
    Signed-off-by: Tom Rini
    Acked-by: Joe Hershberger
    Reviewed-by: Simon Goldschmidt

    Tom Rini
     
  • 8d8ee47e0   env: Add CONFIG_SYS_RELOC_GD_ENV_ADDR symbol ... Browse Code »
    24

    Today in initr_reloc_global_data() we use some non-obvious tests to
    determine if we need to relocate the env_addr within gd or not. In
    order to facilitate migration of other symbols to Kconfig we need to
    introduce a new symbol for this particular use case.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Signed-off-by: Tom Rini

    Tom Rini
     

18 Oct, 2019

1 commit

23 Sep, 2019

1 commit

14 Aug, 2019

1 commit

09 Aug, 2019

1 commit

  • 00f237e22   qemu-x86: Use config_distro_bootcmd ... Browse Code »

    Converts qemu x86 machines to boot using distro_config. The intent is to
    allow u-boot in qemu to be maximally compatible with many boot methods
    without having to change the config. Previously, u-boot would only boot
    in a very limited set of circumstances where there was a /boot/vmlinuz
    on scsi 0:3 with no ramdisk.

    Signed-off-by: Joshua Watt
    Reviewed-by: Bin Meng
    [bmeng: convert doc updates to reST]
    Signed-off-by: Bin Meng

    Joshua Watt
     

02 Aug, 2019

1 commit

21 Jun, 2019

1 commit

27 May, 2019

1 commit

19 May, 2019

1 commit

30 Apr, 2019

2 commits

13 Feb, 2019

1 commit

  • 0ea8741ff   efi_loader: CMD_BOOTEFI_HELLO_COMPILE in configs ... Browse Code »

    It should not be necessary to adjust CMD_BOOTEFI_HELLO_COMPILE in config
    files.

    arch/arm/lib/crt0_arm_efi.S cannot be compiled in thumbs mode. We can
    disable CMD_BOOTEFI_HELLO_COMPILE for CONFIG_CPU_V7M. So there is no longer
    a need to disable it in stm32 configs.

    helloworld.efi can be built without problems on x86_64. So there is no need
    to disable it in chromebook_link64_defconfig and qemu-x86_64_defconfig.

    Same is true for ARM V7A. So do not disable CMD_BOOTEFI_HELLO_COMPILE in
    kp_imx6q_tpc_defconfig.

    Some architecture checks are already make for EFI_LOADER. There is no need
    to repeat them for CMD_BOOTEFI_HELLO_COMPILE

    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass
    Reviewed-by: Patrice.Chotard@st.com
    Signed-off-by: Alexander Graf

    Heinrich Schuchardt
     

13 Dec, 2018

1 commit

  • d50d6817b   spl: fix build failure with !CONFIG_SPL_PCI_SUPPORT ... Browse Code »

    Building U-Boot with CONFIG_PCI and CONFIG_DM_PCI enabled, but
    CONFIG_SPL_PCI_SUPPORT disabled, results in following linker
    error:

    lib/built-in.o: In function `fdtdec_get_pci_bar32':
    lib/fdtdec.c:305: undefined reference to `dm_pci_read_bar32'
    fdtdec.c:305:(.text.fdtdec_get_pci_bar32+0x24): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `dm_pci_read_bar32'

    This is because reference to dm_pci_read_bar32() remains in lib/fdtdec.c
    while SPL build does not descend into drivers/pci directory in
    drivers/Makefile if CONFIG_SPL_PCI_SUPPORT is not enabled.

    Fix this by applying appropriate #define guards in lib/fdtdec.c.
    It looks like ns16550.c has the same problem, so fixed that too.

    To simplify this, CONFIG_SPL_PCI_SUPPORT is renamed to CONFIG_SPL_PCI
    (enables use of CONFIG_IS_ENABLED() macro).

    Suggested-by: Vignesh R
    Signed-off-by: Sekhar Nori
    Reviewed-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Sekhar Nori
     

22 Oct, 2018

1 commit

04 Sep, 2018

1 commit

17 Aug, 2018

1 commit

  • 86cf1c828   configs: Migrate CONFIG_NR_DRAM_BANKS ... Browse Code »
    13

    We have the following cases:
    - CONFIG_NR_DRAM_BANKS was defined, migrate normally
    - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
    CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
    - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
    2), set this to 8.

    Signed-off-by: Tom Rini

    Tom Rini
     

24 Jun, 2018

1 commit

  • d6fea4e28   x86: qemu: Change default vesa mode to 1024x768x32 ... Browse Code »

    The default vesa mode was changed since commit 55b4e1b7d999
    ("x86: Change default FRAMEBUFFER_VESA_MODE of some boards") for
    better VxWorks compatibility but with the changes QEMU video console
    no longer works. This is because QEMU's vgabios implements the VESA
    mode 8:8:8 as 24bpp without an alpha channel, which U-Boot's video
    console driver currently does not support yet.

    We need change to real 32bpp in order to make it work again. QEMU
    vgabios implements the custom 32bpp VESA mode starting from 0x140
    (320x200x32) to 0x147 (1600x1200x32). Set it to 0x144 (1024x768x32).

    Fixes: 55b4e1b7d999 ("x86: Change default FRAMEBUFFER_VESA_MODE of some boards")
    Signed-off-by: Bin Meng
    Reviewed-by: Simon Glass

    Bin Meng
     

04 Jun, 2018

1 commit

28 Apr, 2018

1 commit

  • f1b1f7706   Convert CONFIG_SPI to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_SPI

    This partly involves updating code that assumes that CONFIG_SPI implies
    things that are specific to the MPC8xx SPI driver. For now, just update
    the CONFIG tests. This also involves reworking the default for
    CONFIG_SYS_DEF_EEPROM_ADDR so that we don't set it when we cannot make a
    reasonable default, as it does not cause any compile failures.

    Signed-off-by: Adam Ford
    Signed-off-by: Tom Rini

    Adam Ford
     

17 Apr, 2018

1 commit

16 Apr, 2018

1 commit

09 Apr, 2018

2 commits

24 Feb, 2018

1 commit

  • d021e9421   Convert CONFIG_BOOTP_BOOTPATH et al to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_BOOTP_BOOTPATH
    CONFIG_BOOTP_DNS
    CONFIG_BOOTP_GATEWAY
    CONFIG_BOOTP_HOSTNAME
    CONFIG_BOOTP_PXE
    CONFIG_BOOTP_SUBNETMASK
    CONFIG_CMDLINE_EDITING
    CONFIG_AUTO_COMPLETE
    CONFIG_SYS_LONGHELP
    CONFIG_SUPPORT_RAW_INITRD
    CONFIG_ENV_VARS_UBOOT_CONFIG

    Signed-off-by: Adam Ford
    [trini: Re-run the migration]
    Signed-off-by: Tom Rini

    Adam Ford
     

11 Feb, 2018

1 commit

  • 278b90ce7   configs: Migrate CONFIG_SYS_TEXT_BASE ... Browse Code »
    15

    On the NIOS2 and Xtensa architectures, we do not have
    CONFIG_SYS_TEXT_BASE set. This is a strict migration of the current
    values into the defconfig and removing them from the headers.

    I did not attempt to add more default values in and for now will leave
    that to maintainers.

    Signed-off-by: Tom Rini

    Tom Rini
     

19 Oct, 2017

1 commit

  • 871aa41d4   x86: provide CONFIG_BUILD_ROM ... Browse Code »

    Up to now we depended on an exported variable to build u-boot.rom.
    We should be able to specify it in the configuration file, too.

    With this patch this becomes possible using the new Kconfig option
    CONFIG_BUILD_ROM.

    This option depends on CONFIG_X86 and is selected in
    qemu-x86_defconfig and qemu-x86_64_defconfig.

    Cc: Simon Glass
    Cc: Bin Meng
    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Bin Meng

    Heinrich Schuchardt
     

17 Oct, 2017

1 commit

13 Oct, 2017

1 commit

11 Oct, 2017

1 commit

  • ad12dc184   cmd: Toggle the default value of CONFIG_CMD_IMLS ... Browse Code »

    Having this as a 'default y' is rather annoying because it doesn't
    actually compile unless other options are defined in the board header:

    ../cmd/bootm.c: In function 'do_imls_nor':
    ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
    i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {

    Make it 'default n' so people who develop new boards that start from a
    blank defconfig have one less compilation failure to debug.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

05 Oct, 2017

1 commit

  • 4a59ada5e   efi_selftest: enable CONFIG_CMD_BOOTEFI_SELFTEST ... Browse Code »

    The EFI selftest has been broken by a patch on efi-next.
    We should enable CONFIG_CMD_BOOTEFI_SELFTEST on
    qemu-x86_defconfig and qemu-x86_64_defconfig by default
    to catch this type of problem in the Travis CI tests.

    These systems typically have abundant memory so that
    enabling this option should not pose a problem.

    Signed-off-by: Heinrich Schuchardt
    Reviewed-by: Simon Glass
    Signed-off-by: Alexander Graf

    Heinrich Schuchardt
     

24 Aug, 2017

1 commit

15 Aug, 2017

2 commits

13 Aug, 2017

1 commit

  • e9e5d9d29   dm: timer: normalise SPL and TPL support ... Browse Code »

    To fully support DM timer in SPL and TPL, we need a few things cleaned
    up and normalised:
    - inclusion of the uclass and drivers should be an all-or-nothing
    decision for each stage and under control of $(SPL_TPL_)TIMER
    instead of having the two-level configuration with TIMER and
    $(SPL_TPL_)TIMER_SUPPORT
    - when $(SPL_TPL_)TIMER is enabled, the ARMv8 generic timer code can
    not be compiled in

    This normalises configuration to $(SPL_TPL_)TIMER and moves the config
    options to drivers/timer/Kconfig (and cleans up the collateral damage
    to some defconfigs that had SPL_TIMER_SUPPORT enabled).

    Signed-off-by: Philipp Tomsich
    Reviewed-by: Simon Glass

    Philipp Tomsich
     

12 Aug, 2017

1 commit

01 Aug, 2017

2 commits