1. 09 Aug, 2012 1 commit
  2. 07 Jul, 2012 1 commit
  3. 21 Jun, 2012 1 commit
  4. 25 Apr, 2012 1 commit
    • Liu Gang's avatar
      powerpc/corenet_ds: Slave reads ENV from master when boot from SRIO · 0a85a9e7
      Liu Gang authored
      When boot from SRIO, slave's ENV can be stored in master's memory space,
      then slave can fetch the ENV through SRIO interface.
      
      NOTE: Because the slave can not erase, write master's NOR flash by SRIO
      	  interface, so it can not modify the ENV parameters stored in
      	  master's NOR flash using "saveenv" or other commands.
      
      Master needs to:
      	1. Put the slave's ENV into it's own memory space.
      	2. Set an inbound SRIO window covered slave's ENV stored in master's
      	   memory space.
      Slave needs to:
      	1. Set a specific TLB entry in order to fetch ucode and ENV from master.
      	2. Set a LAW entry with the TargetID SRIO1 or SRIO2 for ucode and ENV.
      Signed-off-by: default avatarLiu Gang <Gang.Liu@freescale.com>
      Signed-off-by: default avatarShaohui Xie <Shaohui.Xie@freescale.com>
      0a85a9e7
  5. 30 Mar, 2012 1 commit
    • Maximilian Schwerin's avatar
      Add support for loading and saving the environment to a FAT partition · 57210c7c
      Maximilian Schwerin authored
      The following must be defined:
      
      CONFIG_ENV_IS_IN_FAT
      	Enable this saving environment to FAT.
      
      FAT_ENV_INTERFACE
      	Interface the FAT resides on (e.g. mmc).
      
      FAT_ENV_DEVICE
      	The interface device number (e.g. 0 for mmc0)
      
      FAT_ENV_PART
      	The device part (e.g. 1 for mmc0:1)
      
      FAT_ENV_FILE
      	The filename of the environment file.
      
      Author:    Maximilian Schwerin <mvs@tigris.de>
      
      Removed dead DEBUG comment.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      57210c7c
  6. 27 Mar, 2012 1 commit
  7. 26 Mar, 2012 1 commit
  8. 18 Mar, 2012 1 commit
    • Simon Glass's avatar
      bootstage: Implement core microsecond boot time measurement · 3a608ca0
      Simon Glass authored
      This defines the basics of a new boot time measurement feature. This allows
      logging of very accurate time measurements as the boot proceeds, by using
      an available microsecond counter.
      
      To enable the feature, define CONFIG_BOOTSTAGE in your board config file.
      Also available is CONFIG_BOOTSTAGE_REPORT which will cause a report to be
      printed just before handing off to the OS.
      
      Most IDs are not named at this stage. For that I would first like to
      renumber them all.
      
      Timer summary in microseconds:
             Mark    Elapsed  Stage
                0          0  reset
          205,000    205,000  board_init_f
        6,053,000  5,848,000  bootm_start
        6,053,000          0  id=1
        6,058,000      5,000  id=101
        6,058,000          0  id=100
        6,061,000      3,000  id=103
        6,064,000      3,000  id=104
        6,093,000     29,000  id=107
        6,093,000          0  id=106
        6,093,000          0  id=105
        6,093,000          0  id=108
        7,089,000    996,000  id=7
        7,089,000          0  id=15
        7,089,000          0  id=8
        7,097,000      8,000  start_kernel
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      3a608ca0
  9. 03 Mar, 2012 1 commit
  10. 10 Dec, 2011 1 commit
  11. 06 Dec, 2011 1 commit
    • Vadim Bendebury's avatar
      Add a cli command to test the TPM device. · 576fb1ed
      Vadim Bendebury authored
      The command gets an arbitrary number of arguments (up to 30), which
      are interpreted as byte values and are feed into the TPM device after
      proper initialization. Then the return value and data of the TPM
      driver is examined.
      
      TPM commands are described in the TCG specification.
      
      For instance, the following sequence is the 'TPM Startup' command, it
      is processed by the TPM and a response is generated:
      
      boot > tpm 0x0 0xc1 0x0 0x0 0x0 0xc 0x0 0x0 0x0 0x99 0x0 0x1
      Found TPM SLB9635 TT 1.2 by Infineon
      Got TPM response:
       00 c4 00 00 00 0a 00 00 00 00
      
      If the command is corrupted (fed one byte short), an error is reported:
      boot > tpm 0x0 0xc1 0x0 0x0 0x0 0xc 0x0 0x0 0x0 0x99 0x0
      generic_lpc_tpm.c:311 unexpected TPM status 0xff000888
      generic_lpc_tpm.c:516 failed sending data to TPM
      tpm command failed
      boot >
      
      Change-Id: I3f3c5bfec8b852e208c4e99ba37b0f2b875140b0
      Signed-off-by: default avatarVadim Bendebury <vbendeb@chromium.org>
      CC: Wolfgang Denk <wd@denx.de>
      576fb1ed
  12. 27 Oct, 2011 1 commit
    • Aneesh V's avatar
      omap: spl: fix build break due to changes in FAT · 2d01dd95
      Aneesh V authored
      FAT library now uses malloc() and free(). But SPL doesn't
      have heap until now. Setup a heap in SDRAM to fix this issue.
      
      However this increases SPL footprint beyond the available SRAM
      budget. So, compile out some fancy features in the SDARM init
      bring back footprint under control
      
      CC: Sandeep Paulraj <s-paulraj@ti.com>
      CC: Wolfgang Denk <wd@denx.de>
      Signed-off-by: default avatarAneesh V <aneesh@ti.com>
      Signed-off-by: default avatarSandeep Paulraj <s-paulraj@ti.com>
      2d01dd95
  13. 17 Oct, 2011 3 commits
  14. 09 Oct, 2011 1 commit
  15. 30 Sep, 2011 1 commit
  16. 04 Sep, 2011 1 commit
  17. 26 Jul, 2011 2 commits
  18. 22 Jun, 2011 1 commit
  19. 20 Apr, 2011 2 commits
    • Andy Fleming's avatar
      Add mdio command for new PHY infrastructure · 995daa0b
      Andy Fleming authored
      The new mdio command doesn't have all of the features of the mii
      command, but it provides the necessary read/write primitives, and allows
      users to interact with 10G PHYs, and other PHYs which use Clause 45 of
      802.3.  This means that the mdio command requires a "Device Address"
      argument, though for clause 22 PHYs, the argument can be "-".
      Signed-off-by: default avatarAndy Fleming <afleming@freescale.com>
      Acked-by: default avatarDetlev Zundel <dzu@denx.de>
      995daa0b
    • Andy Fleming's avatar
      Create PHY Lib for U-Boot · 5f184715
      Andy Fleming authored
      Extends the mii_dev structure to participate in a full-blown MDIO and
      PHY driver scheme.  The mii_dev structure and miiphy calls are modified
      in such a way to allow the original mii command and miiphy
      infrastructure to work as before, but also to support a new set of APIs
      which allow (among other things) sharing of PHY driver code and 10G support
      
      The mii command will continue to support normal PHY management functions
      (Clause 22 of 802.3), but will not be changed to support 10G
      (Clause 45).
      
      The basic design is similar to PHY Lib from Linux, but simplified for
      U-Boot's network and driver infrastructure.
      
      We now have MDIO drivers and PHY drivers
      
      An MDIO driver provides:
      read
      write
      reset
      
      A PHY driver provides:
      (optionally): probe
      config - initial setup, starting of auto-negotiation
      startup - waiting for AN, and reading link state
      shutdown - any cleanup needed
      
      The ethernet drivers interact with the PHY Lib using these functions:
      phy_connect()
      phy_config()
      phy_startup()
      phy_shutdown()
      
      Each PHY driver can be configured separately, or all at once using
      config_phylib_all_drivers.h (added in the patch which adds the drivers)
      
      We also provide generic drivers for Clause 22 (10/100/1000), and
      Clause 45 (10G) PHYs.
      
      We also implement phy_reset(), and call it in phy_connect(). Because
      phy_reset() is essentially the same as miiphy_reset, but:
      a) must support 10G PHYs, and
      b) should use the phylib primitives,
      
      we implement miiphy_reset, using phy_reset(), but only when
      CONFIG_PHYLIB is set. Otherwise, we just use the old version. In this
      way, we save on compile size, even if we don't manage to save code size.
      
      Pulled ethtool.h and mdio.h from:
      git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6
      782d640afd15af7a1faf01cfe566ca4ac511319d
      With many, many deletions so as to enable compilation under u-boot
      Signed-off-by: default avatarAndy Fleming <afleming@freescale.com>
      Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
      Acked-by: default avatarDetlev Zundel <dzu@denx.de>
      5f184715
  20. 13 Apr, 2011 3 commits
  21. 08 Apr, 2011 1 commit
  22. 09 Jan, 2011 1 commit
    • Mike Frysinger's avatar
      config_cmd_defaults.h: new header for common u-boot command defaults · 52f0aa83
      Mike Frysinger authored
      We have config_defaults.h which are random configuration settings that
      everyone gets by default.  We also have config_cmd_default.h which is a
      recommended list of defaults but boards have to opt into.  Now we have
      config_cmd_defaults.h which is a list of defaults that everyone gets
      and has to actively opt out of.
      
      For now, we populate it with the bootm command which previously was
      unable to be disabled.
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      52f0aa83
  23. 26 Nov, 2010 1 commit
  24. 17 Nov, 2010 1 commit
    • Sebastien Carlier's avatar
      Switch from archive libraries to partial linking · 6d8962e8
      Sebastien Carlier authored
      Before this commit, weak symbols were not overridden by non-weak symbols
      found in archive libraries when linking with recent versions of
      binutils.  As stated in the System V ABI, "the link editor does not
      extract archive members to resolve undefined weak symbols".
      
      This commit changes all Makefiles to use partial linking (ld -r) instead
      of creating library archives, which forces all symbols to participate in
      linking, allowing non-weak symbols to override weak symbols as intended.
      This approach is also used by Linux, from which the gmake function
      cmd_link_o_target (defined in config.mk and used in all Makefiles) is
      inspired.
      
      The name of each former library archive is preserved except for
      extensions which change from ".a" to ".o".  This commit updates
      references accordingly where needed, in particular in some linker
      scripts.
      
      This commit reveals board configurations that exclude some features but
      include source files that depend these disabled features in the build,
      resulting in undefined symbols.  Known such cases include:
      - disabling CMD_NET but not CMD_NFS;
      - enabling CONFIG_OF_LIBFDT but not CONFIG_QE.
      Signed-off-by: default avatarSebastien Carlier <sebastien.carlier@gmail.com>
      6d8962e8
  25. 19 Sep, 2010 1 commit
  26. 17 Jan, 2010 2 commits
  27. 02 Dec, 2009 1 commit
  28. 22 Nov, 2009 1 commit
  29. 13 Nov, 2009 1 commit
  30. 27 Oct, 2009 1 commit
  31. 18 Oct, 2009 1 commit
    • Mike Frysinger's avatar
      env: only build env_embedded and envcrc when needed · 6dab6add
      Mike Frysinger authored
      The env code is protected by the ENV_IS_EMBEDDED define, so attempting to
      compile the code when this isn't defined is pointless.  Now that the env
      headers have unified around CONFIG_ENV_IS_EMBEDDED, convert the build
      system to only build the env objects when this is enabled.  And now that
      the env code is conditionally compiled, we can drop the source code checks.
      
      For people who want to extract the environment manually, add a new option
      CONFIG_BUILD_ENVCRC that only enables the envcrc utility.
      Signed-off-by: default avatarMike Frysinger <vapier@gentoo.org>
      6dab6add
  32. 19 Jul, 2009 1 commit
  33. 17 Jul, 2009 1 commit
    • Jean-Christophe PLAGNIOL-VILLARD's avatar
      stdio/device: rework function naming convention · 52cb4d4f
      Jean-Christophe PLAGNIOL-VILLARD authored
      So far the console API uses the following naming convention:
      
      	======Extract======
      	typedef struct device_t;
      
      	int	device_register (device_t * dev);
      	int	devices_init (void);
      	int	device_deregister(char *devname);
      	struct list_head* device_get_list(void);
      	device_t* device_get_by_name(char* name);
      	device_t* device_clone(device_t *dev);
      	=======
      
      which is too generic and confusing.
      
      Instead of using device_XX and device_t we change this
      into stdio_XX and stdio_dev
      
      This will also allow to add later a generic device mechanism in order
      to have support for multiple devices and driver instances.
      Signed-off-by: default avatarJean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
      
      Edited commit message.
      Signed-off-by: default avatarWolfgang Denk <wd@denx.de>
      52cb4d4f