You need to sign in or sign up before continuing.
  1. 21 6月, 2006 1 次提交
  2. 10 6月, 2006 1 次提交
    • D
      [TG3]: Handle Sun onboard tg3 chips more correctly. · f49639e6
      David S. Miller 提交于
      Get rid of all the SUN_570X logic and instead:
      
      1) Make sure MEMARB_ENABLE is set when we probe the SRAM
         for config information.  If that is off we will get
         timeouts.
      
      2) Always try to sync with the firmware, if there is no
         firmware running do not treat it as an error and instead
         just report it the first time we notice this condition.
      
      3) If there is no valid SRAM signature, assume the device
         is onboard by setting TG3_FLAG_EEPROM_WRITE_PROT.
      
      Update driver version and release date.
      
      With help from Michael Chan and Fabio Massimo Di Nitto.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f49639e6
  3. 09 6月, 2006 2 次提交
  4. 06 6月, 2006 5 次提交
  5. 27 5月, 2006 4 次提交
  6. 26 5月, 2006 1 次提交
  7. 24 5月, 2006 2 次提交
  8. 23 5月, 2006 3 次提交
  9. 22 5月, 2006 1 次提交
  10. 20 5月, 2006 11 次提交
  11. 19 5月, 2006 1 次提交
  12. 18 5月, 2006 1 次提交
  13. 16 5月, 2006 5 次提交
  14. 13 5月, 2006 1 次提交
  15. 11 5月, 2006 1 次提交
    • J
      sis900: phy for FoxCon motherboard · d8e95e52
      James Cameron 提交于
      661FX7MI-S motherboard which uses the SiS 661FX chipset.  The patch adds
      an entry to mii_chip_info for the transceiver.
      
      The PHY ids were found using the sis900_c_122.diff patch from
      http://brownhat.org/sis900.html but that patch didn't solve the problem,
      because the PHY at address 1 was already being chosen.
      
      Without my patch, when bursts of packets arrive from other hosts on a
      LAN, the interface dropped one roughly 10% of the time, causing
      retransmits.  There were fifth second pauses in refresh of large xterms,
      and it made Netrek suck.  I can provide further test data.
      
      Workaround in lieu of patch is to use mii-tool to advertise
      100baseTx-HD, then force renegotiation.
      
      I wasn't able to identify the actual transceiver, so the description
      field is a guess.
      
      This patch is similar to Artur Skawina's patch:
      http://marc.theaimsgroup.com/?l=linux-netdev&m=114297516729079&w=2
      
      I'm not sure, but I wonder if it means the default behaviour should be
      changed, so as to better handle future transceivers.
      
      Diff is against 2.6.16.13.
      Signed-off-by: NJames Cameron <james.cameron@hp.com>
      Signed-off-by: NStephen Hemminger <shemminger@osdl.org>
      d8e95e52