1. 25 4月, 2009 2 次提交
  2. 24 4月, 2009 2 次提交
  3. 20 4月, 2009 2 次提交
    • M
      NetLoop initialization bug · 3c172c4f
      Michael Zaidman 提交于
      The patch fixes the bug of partial initialization of global network
      parameters.
      
      Upon u-boot's start up the first ping command causes a failure of the
      consequent TFTP command. It happens in the recently added mechanism of
      the NetLoop initialization where initialization of global network
      parameters is separated in the NetInitLoop routine which is called per
      env_id change. Thus, ping request will initialize the network parameters
      necessary for ping operation only, afterwards the env_changed_id will be
      set to the env_id that will prevent all following initialization requests
      from other protocols.
      The problem is that the initialized by ping subset of network parameters
      is not sufficient for other protocols and particularly for TFTP which
      requires the NetServerIp also.
      Signed-off-by: NMichael Zaidman <michael.zaidman@gmail.com>
      Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
      3c172c4f
    • T
      net: fix ULI 526x macro usage in netdev.h · b11f664f
      Timur Tabi 提交于
      Change netdev.h to use CONFIG_ULI526X instead of CONFIG_ULI526.  CONFIG_ULI526X
      is used everywhere else, so that's the correct macro name.  Without this fix,
      Ethernet will not work on the Freescale MPC8610 HPCD.
      Signed-off-by: NTimur Tabi <timur@freescale.com>
      Signed-off-by: NBen Warren <biggerbadderben@gmail.com>
      b11f664f
  4. 17 4月, 2009 6 次提交
  5. 16 4月, 2009 5 次提交
  6. 08 4月, 2009 1 次提交
  7. 07 4月, 2009 9 次提交
  8. 06 4月, 2009 2 次提交
    • T
      Blackfin: spi: make cs deassert function deterministic · d04371a1
      Todor I Mollov 提交于
      Blackfin SPI driver was not driving the SPI chip-select high before
      putting the chip-select signals into tri-state mode.  This is probably
      something that slipped by unnoticed in most designs.  If the signals are
      put directly into a tri-state mode, then the board is relying on the
      pull-up resistors to pull up the chip-select before the next transaction.
      Most of the time this is fine, except when you have two transactions that
      follow each other very closely, such as the flash erase and read status
      register commands.  In this case I was seeing a 500ns separation between
      the transactions.  In my setup, with a 10kOhm pull-up, it would meet
      timing spec about half the time and resulted in intermittent errors.  (A
      stronger pull up would fix this, but our design is targeted for low power
      consumption and a 3.3kOhm @ 3.3v is 3.3mW of needless power consumption.)
      I modified the spi_cs_deactivate() function in bfin_spi.c to drive the
      chip-selects high before putting them into tri-state.  For me, this
      resulted in a rise time of 5ns instead of the previous rise time of about
      1us, and fully satisfied the timing spec of the chip.
      Signed-off-by: NTodor I Mollov <tmollov@ucsd.edu>
      Signed-off-by: NMike Frysinger <vapier@gentoo.org>
      d04371a1
    • W
      712ac6a1
  9. 05 4月, 2009 11 次提交