1. 08 1月, 2016 2 次提交
  2. 18 12月, 2015 1 次提交
  3. 30 10月, 2015 2 次提交
  4. 29 10月, 2015 2 次提交
  5. 30 9月, 2015 1 次提交
  6. 09 9月, 2015 2 次提交
  7. 22 7月, 2015 2 次提交
    • S
      net: Allow drivers to return -ENOSYS with the write_hwaddr() method · b86f795a
      Simon Glass 提交于
      Some drivers may want to implement this method for some of their devices but
      not for others. So it is not possible to just leave the operation out of
      the table. Drivers could get around this by masquerading as two separate
      drivers but that seems unpleasant.
      
      Allow the driver to return an error when it does not want to process the
      write_hwaddr() method.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      b86f795a
    • S
      dm: eth: Avoid blocking on packet reception · a1ca92ea
      Simon Glass 提交于
      Some devices can take a long time to work out whether they have a new packet
      or now. For example the ASIX USB Ethernet dongle can take 5 seconds to do
      this, since it waits until it gets a new packet on the wire before allowing
      the USB bulk read packet to be submitted.
      
      At present with driver mode the Ethernet receive code reads 32 packets. This
      can take a very long time if we must wait for all 32 packets. The old code
      (before driver model) worked by reading a single set of packets from the USB
      device, then processing all the packets with in. It would be nice to use
      the same behaviour with driver model.
      
      Add a flag to the receive method which indicates that the driver should try
      to find a packet if available, by consulting the hardware. When the flag is
      not set, it should just return any packet data it has already received. If
      there is none, it should return -EAGAIN so that the loop will terminate.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      a1ca92ea
  8. 21 5月, 2015 2 次提交
  9. 20 5月, 2015 2 次提交
  10. 19 4月, 2015 17 次提交
  11. 25 10月, 2014 1 次提交
  12. 22 7月, 2014 1 次提交
  13. 13 5月, 2014 1 次提交
  14. 07 2月, 2014 1 次提交
    • A
      net: execute "miiphy_init" if CONFIG_PHYLIB defined · 27ee59af
      Alexey Brodkin 提交于
      In "common/Makefile" "miiphyutil.o" gets built if any of the following
      items enabled:
       * CONFIG_PHYLIB
       * CONFIG_MII
       * CONFIG_CMD_MII
      
      So it's possible to not define CONFIG_MII or CONFIG_CMD_MII and still
      use functions like "miiphy_get_dev_by_name".
      
      In its turn "miiphy_get_dev_by_name" traverses "mii_devs" list which is
      not initialized because "miiphy_init" never got called.
      
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Wolfgang Denk <wd@denx.de>
      Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
      Signed-off-by: NAlexey Brodkin <abrodkin@synopsys.com>
      27ee59af
  15. 24 7月, 2013 1 次提交
  16. 28 9月, 2012 1 次提交
  17. 25 9月, 2012 1 次提交
    • J
      net: Improve the speed of netconsole · f8be7d65
      Joe Hershberger 提交于
      Previously u-boot would initialize the network interface for every
      network operation and then shut it down again.  This makes sense for
      most operations where the network in not known to be needed soon after
      the operation is complete.  In the case of netconsole, it will use the
      network for every interaction with the shell or every printf.  This
      means that the network is being reinitialized very often.  On many
      devices, this intialization is very slow.
      
      This patch checks for consecutive netconsole actions and leaves the
      ethernet hardware initialized between them.  It will still behave the
      same old way for all other network operations and any time another
      network operation happens between netconsole operations.
      Signed-off-by: NJoe Hershberger <joe.hershberger@ni.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Acked-by: NStefano Babic <sbabic@denx.de>
      f8be7d65