1. 28 9月, 2010 1 次提交
  2. 10 8月, 2010 1 次提交
    • H
      net ppc: fix ethernet device names with spaces · 48690d80
      Heiko Schocher 提交于
      since commit 1384f3bb ethernet names
      with spaces drop a
      
      Warning: eth device name has a space!
      
      message. This patch fix it for:
      
      - "FEC ETHERNET" devices found on
        mpc512x, mpc5xxx, mpc8xx and mpc8220 boards.
        renamed to "FEC".
      - "SCC ETHERNET" devices found on
        mpc8xx, mpc82xx based boards. Renamed to "SCC".
      - "HDLC ETHERNET" devices found on mpc8xx boards
        Renamed to "HDLC"
      - "FCC ETHERNET" devices found on mpc8260 and mpc85xx based
        boards. Renamed to "FCC"
      
      Tested on the kup4k board.
      Signed-off-by: NHeiko Schocher <hs@denx.de>
      Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
      48690d80
  3. 04 8月, 2010 1 次提交
    • W
      Rename getenv_r() into getenv_f() · cdb74977
      Wolfgang Denk 提交于
      While running from flash, i. e. before relocation, we have only a
      limited C runtime environment without writable data segment. In this
      phase, some configurations (for example with environment in EEPROM)
      must not use the normal getenv(), but a special function.  This
      function had been called getenv_r(), with the idea that the "_r"
      suffix would mean the same as in the _r_eentrant versions of some of
      the C library functions (for example getdate vs. getdate_r, getgrent
      vs. getgrent_r, etc.).
      
      Unfortunately this was a misleading name, as in U-Boot the "_r"
      generally means "running from RAM", i. e. _after_ relocation.
      
      To avoid confusion, rename into getenv_f() [as "running from flash"]
      Signed-off-by: NWolfgang Denk <wd@denx.de>
      Acked-by: NDetlev Zundel <dzu@denx.de>
      cdb74977
  4. 22 7月, 2010 1 次提交
  5. 13 6月, 2010 1 次提交
  6. 28 5月, 2010 2 次提交
  7. 04 5月, 2010 1 次提交
  8. 22 4月, 2010 1 次提交
  9. 19 4月, 2010 1 次提交
    • R
      fsl_i2c: Added a callpoint for i2c_board_late_init · 26a33504
      Richard Retanubun 提交于
      This patch adds a callpoint in i2c_init that allows board specific
      i2c board initialization (typically for i2c bus reset) that is called
      after i2c_init operations, allowing the i2c_board_late_init function
      to use the pre-configured i2c bus speed and slave address.
      26a33504
  10. 13 4月, 2010 4 次提交
  11. 08 4月, 2010 1 次提交
  12. 22 3月, 2010 1 次提交
  13. 01 2月, 2010 1 次提交
  14. 27 1月, 2010 1 次提交
  15. 18 1月, 2010 1 次提交
    • H
      cmd_eeprom: I2C updates · 548738b4
      Heiko Schocher 提交于
      - CONFIG_ENV_EEPROM_IS_ON_I2C
        define this, if you have I2C and SPI activated, and your
        EEPROM, which holds the environment, is on the I2C bus.
      
      - CONFIG_I2C_ENV_EEPROM_BUS
        if you have an Environment on an EEPROM reached over
        I2C muxes, you can now define, how to reach this
        EEPROM.
      Signed-off-by: NHeiko Schocher <hs@denx.de>
      548738b4
  16. 09 12月, 2009 1 次提交
  17. 08 12月, 2009 1 次提交
  18. 05 12月, 2009 1 次提交
  19. 03 12月, 2009 1 次提交
  20. 28 10月, 2009 2 次提交
  21. 19 10月, 2009 1 次提交
    • M
      env: only build env_embedded and envcrc when needed · 6dab6add
      Mike Frysinger 提交于
      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: NMike Frysinger <vapier@gentoo.org>
      6dab6add
  22. 03 10月, 2009 5 次提交
  23. 25 9月, 2009 1 次提交
  24. 23 9月, 2009 2 次提交
  25. 06 9月, 2009 1 次提交
    • E
      Reset i2c slave devices during init on mpc5xxx cpus · 5da71efa
      Eric Millbrandt 提交于
      Reset any i2c devices that may have been interrupted during a system reset.
      Normally this would be accomplished by clocking the line until SCL and SDA
      are released and then sending a start condtiion (From an Atmel datasheet).
      There is no direct access to the i2c pins so instead create start commands
      through the i2c interface.  Send a start command then delay for the SDA Hold
      time, repeat this by disabling/enabling the bus a total of 9 times.
      Signed-off-by: NEric Millbrandt <emillbrandt@dekaresearch.com>
      5da71efa
  26. 02 9月, 2009 1 次提交
  27. 25 8月, 2009 2 次提交
  28. 23 7月, 2009 1 次提交
  29. 17 7月, 2009 1 次提交