1. 30 5月, 2005 3 次提交
  2. 27 5月, 2005 2 次提交
  3. 24 5月, 2005 5 次提交
  4. 19 5月, 2005 4 次提交
    • D
    • D
      [TG3]: Refine DMA boundary setting. · 59e6b434
      David S. Miller 提交于
      Extract DMA boundary bit selection into a seperate
      function, tg3_calc_dma_bndry().  Call this from
      tg3_test_dma().
      
      Make DMA test more reliable by using no DMA boundry
      setting during the test.  If the test passes, then
      use the setting we selected before the test.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      Signed-off-by: NMichael Chan <mchan@broadcom.com>
      59e6b434
    • D
      [TG3]: Set minimal hw interrupt mitigation. · 15f9850d
      David S. Miller 提交于
      Even though we do software interrupt mitigation
      via NAPI, it still helps to have some minimal
      hw assisted mitigation.
      
      This helps, particularly, on systems where register
      I/O overhead is much greater than the CPU horsepower.
      
      For example, it helps on NUMA systems.  In such cases
      the PIO overhead to disable interrupts for NAPI accounts
      for the majority of the packet processing cost.  The
      CPU is fast enough such that only a single packet is
      processed by each NAPI poll call.
      
      Thanks to Michael Chan for reviewing this patch.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      15f9850d
    • D
      [TG3]: Add tagged status support. · fac9b83e
      David S. Miller 提交于
      When supported, use the TAGGED interrupt processing support
      the chip provides.  In this mode, instead of a "on/off" binary
      semaphore, an incrementing tag scheme is used to ACK interrupts.
      
      All MSI supporting chips support TAGGED mode, so the tg3_msi()
      interrupt handler uses it unconditionally.  This invariant is
      verified when MSI support is tested.
      
      Since we can invoke tg3_poll() multiple times per interrupt under
      high packet load, we fetch a new copy of the tag value in the
      status block right before we actually do the work.
      
      Also, because the tagged status tells the chip exactly which
      work we have processed, we can make two optimizations:
      
      1) tg3_restart_ints() need not check tg3_has_work()
      2) the tg3_timer() need not poke the chip 10 times per
         second to keep from losing interrupt events
      
      Based upon valuable feedback from Michael Chan <mchan@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      fac9b83e
  5. 16 5月, 2005 17 次提交
    • D
      [PATCH] wireless: 3CRWE154G72 Kconfig help fix · c8920ba0
      Daniel Andersen 提交于
      Version 2 of the 3com OfficeConnect 11g Cardbus Card aka 3CRWE154G72 is not
      supported by the prism54 project.  To stop confusion, the kernel
      documentation should state so as 3com made a good job hiding the version.
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      
      diff -puN drivers/net/wireless/Kconfig~wireless-3crwe154g72-kconfig-help-fix drivers/net/wireless/Kconfig
      c8920ba0
    • J
      [PATCH] Typo in tulip driver · c4cc26d3
      Jiri Benc 提交于
      This patch fixes a typo in tulip driver in 2.6.12-rc3.
      c4cc26d3
    • J
      [PATCH] fix PROMISC/bridging in TLAN driver · 562faf46
      James Harper 提交于
      This has been a problem for me for ages.  When using bridging, the driver
      is switched into promiscuous mode before the link init is complete.  The
      init complete routine then resets the promisc bit on the card so the kernel
      still thinks the card is in promiscuous mode but the card isn't.  doh.
      
      I think this bug only shows up in bridging when the bridge is started at
      boot time (or something else that sets promisc at the same time the card
      was started).  If promisc is enabled later it works.
      
      Here's a trivial (and hopefully correct) patch that works for me. It
      just calls the promisc/multicast setup routine after init.
      
      Cc: Jeff Garzik <jgarzik@pobox.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      562faf46
    • G
      [PATCH] {PATCH] Fix IBM EMAC driver ioctl bug · 99718699
      Geoff Levand 提交于
      Fix IBM EMAC driver ioctl bug.
      
      I found IBM EMAC driver bug.
      So mii-tool command print wrong status.
      
        # mii-tool
        eth0: 10 Mbit, half duplex, no link
        eth1: 10 Mbit, half duplex, no link
      
      I can get correct status on fixed kernel.
      
        # mii-tool
        eth0: negotiated 100baseTx-FD, link okZZ
        eth1: negotiated 100baseTx-FD, link ok
      
      Hiroaki Fuse
      
      Signed-off-by: Geoff Levand <geoffrey.levand@am.sony.com> for CELF
      99718699
    • B
      [PATCH] ns83820 update · c16ef1ce
      Benjamin LaHaise 提交于
      Changes:
      - improved DAC ifdefs from Andi Kleen
      - removal of dead code from Adrian Bunk
      - fix half duplex collision behaviour
      c16ef1ce
    • A
      [PATCH] drivers/net/wireless enabled by wrong option · f7a3aae1
      Al Viro 提交于
      	NET_WIRELESS is only a subset of the stuff in drivers/net/wireless;
      NET_RADIO is what covers all of them.
      Signed-off-by: NAl Viro <viro@parcelfarce.linux.theplanet.co.uk>
      f7a3aae1
    • S
      [PATCH] tlan: restore deleted module parameters. · 15efa9bb
      Stephen Hemminger 提交于
      The module parameter values got lost in the conversion to the new module_param
      interface. This should fix it.
      Signed-off-by: NStephen Hemminger <shemminger@osdl.org>
      
      Index: tlan/drivers/net/tlan.c
      ===================================================================
      15efa9bb
    • A
      [PATCH] SIS900 must select MII · 6da0f685
      Adrian Bunk 提交于
      This patch fixes the following compile error caused by bk-netdev:
      
      <--  snip  -->
      
      ...
        LD      .tmp_vmlinux1
      drivers/built-in.o(.text+0x98528): In function `sis900_get_settings':
      : undefined reference to `mii_ethtool_gset'
      drivers/built-in.o(.text+0x98538): In function `sis900_set_settings':
      : undefined reference to `mii_ethtool_sset'
      drivers/built-in.o(.text+0x98517): In function `sis900_get_link':
      : undefined reference to `mii_link_ok'
      drivers/built-in.o(.text+0x98547): In function `sis900_nway_reset':
      : undefined reference to `mii_nway_restart'
      make: *** [.tmp_vmlinux1] Error 1
      
      <--  snip  -->
      Signed-off-by: NAdrian Bunk <bunk@stusta.de>
      Signed-off-by: NDaniele Venzano <venza@brownhat.org>
      6da0f685
    • D
      [PATCH] pcnet32: fix resource leak with loopback test · 1bcd3153
      Don Fry 提交于
      When running the loopback test, resources are not properly released on
      completion.  This patch frees all transmit resources after running the
      loopback test.  Tested on ia32 and ppc64 hardware.
      Signed-off-by: NDon Fry <brazilnut@us.ibm.com>
      1bcd3153
    • D
      [PATCH] wireless/airo: WEXT and quality corrections · 41480af2
      Dan Williams 提交于
      This patch brings the airo driver into line with the current
      WEXT specification of signal quality.  It also fixes the values
      used to determine signal quality and level for MPI & PCMCIA 350
      cards.  It turns out that BSSListRid.rssi was actually in dBm
      for 350 series cards, and that we can use the normalized
      signal strength reported by the card as our "quality" value, on
      a scale of 0 - 100.  Since signal level values are in dBm for
      this driver, max_qual->level MUST be 0, as specified in the WEXT
      spec.  This patch also uses the IW_QUAL constants new in WEXT
      version 17.
      Signed-off-by: NDan Williams <dcbw@redhat.com>
      41480af2
    • H
      [PATCH] Fw: [Bugme-new] [Bug 4482] New: natsemi: incorrect initialization of... · 760f86d7
      Herbert Xu 提交于
      [PATCH] Fw: [Bugme-new] [Bug 4482] New: natsemi: incorrect initialization of IPv6 Neighbor-discovery multicast
      
      On Wed, Apr 13, 2005 at 05:36:42PM +0000, Andrew Morton wrote:
      >            Summary: natsemi: incorrect initialization of IPv6 Neighbor-
      >                     discovery multicast
      
      I've got a pair of FA312 cards and this problem has bothered me
      for ages.  This has finally prompted me to do something about it :)
      
      Turns out that somebody wasn't following the documentation.  We were
      doing 16-bit writes to 32-bit registers which led to some addresses
      working and others not so lucky.
      
      This patch should fix the problem.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      760f86d7
    • S
      [PATCH] atmel wireless · e885b5e8
      simon@thekelleys.org.uk 提交于
      Below is a one-liner for the atmel wireless driver, just adding
      another card to the table.
      e885b5e8
    • M
      [PATCH] forcedeth: Update error handling · 22c6d143
      Manfred Spraul 提交于
      Ayaz wrote an update to the error handling for forcedeth (which I
      modified heavily, thus all bugs are mine):
      The ERROR4 bit is not a fatal error, it just indicates a mismatch
      between the actual packet len and the len according to the 802.3 header.
      The patch adds proper handling.
      The patch also removes the code that drops all packets with RX_ERROR &
      (!RX_FRAMINGERR): ERROR4 errors are also not fatal.
      22c6d143
    • M
      [PATCH] iseries_veth: Cleanup skbs to prevent unregister_netdevice() hanging · b2e0852e
      Michael Ellerman 提交于
      Hi Andrew, Jeff,
      
      The iseries_veth driver is badly behaved in that it will keep TX packets
      hanging around forever if they're not ACK'ed and the queue never fills up.
      
      This causes the unregister_netdevice code to wait forever when we try to take
      the device down, because there's still skbs around with references to our
      struct net_device.
      
      There's already code to cleanup any un-ACK'ed packets in veth_stop_connection()
      but it's being called after we unregister the net_device, which is too late.
      
      The fix is to rearrange the module exit function so that we cleanup any
      outstanding skbs and then unregister the driver.
      Signed-off-by: NMichael Ellerman <michael@ellerman.id.au>
      b2e0852e
    • M
      [PATCH] iseries_veth: Don't leak skbs in RX path · 41664c03
      Michael Ellerman 提交于
      Hi Andrew, Jeff,
      
      Under some strange circumstances the iseries_veth driver can leak skbs.
      
      Fix is simply to call dev_kfree_skb() in the right place.
      Fix up the comment as well.
      Signed-off-by: NMichael Ellerman <michael@ellerman.id.au>
      41664c03
    • M
      [PATCH] iseries_veth: Set dev->trans_start so watchdog timer works right · eb235aef
      Michael Ellerman 提交于
      Hi Andrew, Jeff,
      
      The iseries_veth driver doesn't set dev->trans_start in it's TX path. This
      will cause the net device watchdog timer to fire earlier than we want it to,
      which causes the driver to needlessly reset its connections to other LPARs.
      Signed-off-by: NMichael Ellerman <michael@ellerman.id.au>
      eb235aef
    • M
      [PATCH] iseries_veth: Don't send packets to LPARs which aren't up · f27eff1f
      Michael Ellerman 提交于
      Hi Andrew, Jeff,
      
      The iseries_veth driver has a logic bug which means it will erroneously
      send packets to LPARs for which we don't have a connection.
      
      This usually isn't a big problem because the Hypervisor call fails
      gracefully and we return, but if packets are TX'ed during the negotiation
      of the connection bad things might happen.
      
      Regardless, the right thing is to bail early if we know there's no
      connection.
      Signed-off-by: NMichael Ellerman <michael@ellerman.id.au>
      f27eff1f
  6. 13 5月, 2005 9 次提交