1. 07 5月, 2008 1 次提交
    • A
      uli526x: initialize the hardware prior to requesting interrupts · afd8e399
      Anton Vorontsov 提交于
      The firmware on MPC8610HPCD boards enables ULI ethernet and leaves it
      in some funky state before booting Linux. For drivers, it's always good
      idea to (re)initialize the hardware prior to requesting interrupts.
      
      This patch fixes the following oops:
      
      Oops: Kernel access of bad area, sig: 11 [#1]
      MPC86xx HPCD
      NIP: c0172820 LR: c017287c CTR: 00000000
      [...]
      NIP [c0172820] allocate_rx_buffer+0x2c/0xb0
      LR [c017287c] allocate_rx_buffer+0x88/0xb0
      Call Trace:
      [df82bdc0] [c017287c] allocate_rx_buffer+0x88/0xb0 (unreliable)
      [df82bde0] [c0173000] uli526x_interrupt+0xe4/0x49c
      [df82be20] [c0045418] request_irq+0xf0/0x114
      [df82be50] [c01737b0] uli526x_open+0x48/0x160
      [df82be70] [c0201184] dev_open+0xb0/0xe8
      [df82be80] [c0200104] dev_change_flags+0x90/0x1bc
      [df82bea0] [c035fab0] ip_auto_config+0x214/0xef4
      [df82bf60] [c03421c8] kernel_init+0xc4/0x2ac
      [df82bff0] [c0010834] kernel_thread+0x44/0x60
      Instruction dump:
      4e800020 9421ffe0 7c0802a6 bfa10014 7c7e1b78 90010024 80030060 83e30054
      2b80002f 419d0078 3fa0c039 48000058 <907f0010> 80630088 2f830000 419e0014
      Signed-off-by: NAnton Vorontsov <avorontsov@ru.mvista.com>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      afd8e399
  2. 29 4月, 2008 1 次提交
  3. 17 4月, 2008 2 次提交
    • P
      [netdrvr] tulip: Better MWI workaround for 21143 rev 65 chip errata · 10c64620
      Peter Horton 提交于
      This patch works around the MWI bug on the DC21143 rev 65 Tulip by
      ensuring that the receive buffers don't end on a cache line boundary
      (as documented in the errata).
      
      This patch is required for the MIPS based Cobalt Qube/RaQ as
      supporting the extra PCI commands seems to reduce the chance of a hard
      lockup between the Tulip and the PCI bridge.
      Signed-off-by: NThomas Bogendoerfer <tsbogend@alpha.franken.de>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      10c64620
    • J
      [netdrvr] tulip/winbond-840: don't let tulip.h symbol stomp ours · 48dd59e3
      Jeff Garzik 提交于
      winbond-840 shares tulip.h with the tulip driver, because they share
      many (but not all) of the same register definitions.
      
      This is useful for the register definitions, but not helpful when it
      comes to symbols that are shared among the tulip driver's C modules,
      but not meant to be shared outside that one driver.
      
      Thus, PKT_BUF_SZ is a symbol internal to tulip, but it was intruding
      upon a similar symbol in winbond-840's namespace.  This was not a
      problem as long as the two symbols had the same value, but upcoming
      patches result in differing symbol values.
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      48dd59e3
  4. 29 3月, 2008 1 次提交
    • G
      [netdrvr] tulip_read_eeprom fixes for BUG 4420 · 209261c0
      Grant Grundler 提交于
      If "location" is > "addr_len" bits, the high bits of location would interfere
      with the READ_CMD sent to the eeprom controller.
      
      A patch was submitted to bug:
          http://bugzilla.kernel.org/show_bug.cgi?id=4420
      
      which simply truncated the "location", read whatever was in "location
      modulo addr_len", and returned that value. That avoids confusing the
      eeprom but seems like the wrong solution to me.
      
      Correct would be to not read beyond "1 << addr_len" address of the eeprom.
      I am submitting two changes to implement this:
      1) tulip_read_eeprom will return zero (since we can't return -EINVAL)
         if this is attempted (defensive programming).
      2) In tulip_core.c, fix the tulip_read_eeprom caller so they don't
         iterate past addr_len bits and make sure the entire tp->eeprom[]
         array is cleared.
      
      I konw we don't strictly need both. I would prefer both in the tree
      since it documents the issue and provides a second "defense" from
      the bug from creeping back in.
      Signed-off-by: NGrant Grundler <grundler@parisc-linux.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      209261c0
  5. 17 3月, 2008 2 次提交
  6. 05 3月, 2008 1 次提交
  7. 24 2月, 2008 1 次提交
  8. 06 2月, 2008 1 次提交
  9. 29 1月, 2008 2 次提交
  10. 23 1月, 2008 1 次提交
    • D
      [TULIP] DMFE: Fix SROM parsing regression. · 4c93566e
      David S. Miller 提交于
      Changeset 16b110c3 (dmfe warning fix)
      bothed up the offsets read from the SROM so that it doesn't read the
      same datums it used to.
      
      The change made transformations like turning:
      
      	"srom + 34"
      
      into
      
      	"(__le32 *)srom + 34/4"
      
      which doesn't work because 4 does not divide evenly
      into 34 so we're using a different pointer offset
      than in the original code.
      
      I've changed theses cases in dmfe_parse_srom() to
      consistently use "(type *)(srom + offset)" preserving
      the offsets from the original code.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4c93566e
  11. 13 1月, 2008 3 次提交
  12. 09 1月, 2008 2 次提交
  13. 24 11月, 2007 2 次提交
  14. 13 11月, 2007 1 次提交
  15. 20 10月, 2007 3 次提交
  16. 16 10月, 2007 1 次提交
  17. 15 10月, 2007 2 次提交
  18. 11 10月, 2007 10 次提交
  19. 01 8月, 2007 1 次提交
  20. 16 7月, 2007 1 次提交
  21. 12 7月, 2007 1 次提交