Skip to content
Snippets Groups Projects
  1. Feb 16, 2016
  2. Aug 13, 2015
    • Nikita Kiryanov's avatar
      kconfig: add config option for shell prompt · 181bd9dc
      Nikita Kiryanov authored
      
      Add option to set shell prompt string from menuconfig and migrate
      boards globally.
      
      The migration is done as follows:
      - Boards that explicitly and unconditionally set CONFIG_SYS_PROMPT had the
        entry moved to their defconfig files.
      - Boards that defined some kind of #ifdef logic which selects the
        CONFIG_SYS_PROMPT (for example qemu-mips) got an #undef CONFIG_SYS_PROMPT
        right before the #ifdef logic and were left alone.
      - This change forces CONFIG_SYS_PROMPT to be a per board decision, and thus
        CONFIG_SYS_PROMPT was removed from all <soc>_common.h and <arch>_common.h
        files. This results in a streamlined default value across platforms, and
        includes the following files: spear-common, sunxi-common, mv-common,
        ti_armv7_common, tegra-common, at91-sama5_common, and zynq-common.
      - Boards that relied on <arch/soc>_common.h values of CONFIG_SYS_PROMPT were
        not updated in their respective defconfig files under the assumption that
        since they did not explicitly define a value, they're fine with whatever
        the default is.
      - On the other hand, boards that relied on a value defined in some
        <boards>_common.h file such as woodburn_common, rpi-common,
        bur_am335x_common, ls2085a_common, siemens_am33x_common, and
        omap3_evm_common, had their values moved to the respective defconfig files.
      - The define V_PROMPT was removed, since it is not used anywhere except for
        assigning a value for CONFIG_SYS_PROMPT.
      
      Cc: Tom Rini <trini@konsulko.com>
      Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Signed-off-by: default avatarNikita Kiryanov <nikita@compulab.co.il>
      [trini: Add spring, sniper, smartweb to conversion]
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      181bd9dc
  3. Jun 01, 2015
  4. Mar 04, 2015
  5. Sep 25, 2014
  6. Jul 24, 2013
  7. Apr 15, 2013
  8. Mar 14, 2013
  9. Jan 16, 2013
  10. Oct 15, 2012
  11. Sep 10, 2012
  12. Sep 01, 2012
  13. Jul 09, 2012
  14. Jul 07, 2012
    • Tom Warren's avatar
      arm: Tegra: Use ODMDATA from BCT in IRAM · 76e350b7
      Tom Warren authored
      
      Walk the BIT and BCT to find the ODMDATA word in the
      CustomerData field and put it into Scratch20 reg for
      use by kernel, etc.
      
      Built all Tegra builds OK; Booted on Seaboard and saw
      ODMDATA in PMC scratch20 was the same as the value in my
      burn-u-boot.sh file (0x300D8011). NOTE: All flash utilities
      will have to specify the odmdata (nvflash --odmdata n) on
      the command line or via a cfg file, or built in to their
      BCT.
      
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      Acked-by: default avatarStephen Warren <swarren@wwwdotorg.org>
      76e350b7
    • Tom Warren's avatar
      mmc: tegra2: rename tegra2_mmc.* to tegra_mmc.* · 3f82d89d
      Tom Warren authored
      
      In anticipation of Tegra3 support, continue removing/renaming
      Tegra2-specific files. No functional changes (yet).
      Updated copyrights to 2012.
      
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      3f82d89d
    • Stephen Warren's avatar
      tegra: flesh out bootcmd · bea2674c
      Stephen Warren authored
      
      This implements a useful bootcmd for Tegra. The boot order is:
      
      * If USB enabled, USB storage
      * Internal MMC (SD card or eMMC)
      * If networking is enabled, BOOTP/TFTP
      
      When booting from USB or MMC, the boot script is assumed to be in
      partition 1 (although this may be overridden via the rootpart variable),
      both ext2 and FAT filesystems are supported, the boot script may exist
      in either / or /boot, and the boot script may be named boot.scr.uimg or
      boot.scr.
      
      When booting over the network, it is assumed that boot.scr.uimg exists
      on the TFTP server. There is less flexibility here since those setting
      up network booting are expected to need less hand-holding.
      
      In all cases, it is expected that the initial file loaded is a U-Boot
      image containing a script that will load the kernel, load any required
      initrd, load any required DTB, and finally bootm the kernel.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      bea2674c
    • Stephen Warren's avatar
      tegra: remove some cruft from CONFIG_EXTRA_ENV_SETTINGS · 07a84b7b
      Stephen Warren authored
      
      console isn't used by anything, and the kernel should be set appropriately
      by whatever script is booting the kernel, not imposed by the bootloader.
      
      mem might be useful, but the current value is pretty bogus, since it
      includes nvmem options that make no sense for an upstream kernel, and
      equally should not be required for any downstream kernel. Either way, this
      is also best left to the kernel boot script.
      
      smpflag isn't used by anything, and again was probably intended to be a
      kernel command-line option better set by the kernel boot script.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Signed-off-by: default avatarTom Warren <twarren@nvidia.com>
      07a84b7b
  15. Dec 24, 2011
  16. Dec 09, 2011
  17. Jul 16, 2011
  18. Apr 27, 2011
  19. Mar 27, 2011
  20. Feb 21, 2011
  21. Feb 07, 2011
  22. Oct 25, 2010
  23. Apr 21, 2010
  24. Apr 13, 2010
  25. Dec 14, 2000
  26. Nov 12, 2000
Loading