Skip to content

K
Kernel

openeuler / Kernel
大约 1 年 前同步成功

通知 5
Star 0
Fork 0
K
Kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 20 8月, 2006 3 次提交
  3. 29 7月, 2006 1 次提交
  5. 06 7月, 2006 2 次提交
    • J
      [netdrvr] Remove Becker-template 'io_size' member, when invariant · c3d8e682
      由 Jeff Garzik 提交于 
      Becker-derived drivers often have the 'io_size' member in their chip
info struct, indicating the minimum required size of the I/O resource
(usually a PCI BAR).  For many situations, this number is either
constant or irrelevant (due to pci_iomap convenience behavior).

This change removes the io_size invariant member, and replaces it with a
compile-time constant.

Drivers updated: fealnx, gt96100eth, winbond-840, yellowfin

Additionally,
- gt96100eth: unused 'drv_flags' removed from gt96100eth
- winbond-840: unused struct match_info removed
- winbond-840: mark pci_id_tbl[] const, __devinitdata
Signed-off-by: NJeff Garzik <jeff@garzik.org>
      c3d8e682
    • J
      [netdrvr] Remove Linux-specific changelogs from several Becker template drivers · 03a8c661
      由 Jeff Garzik 提交于 
      When in-kernel net drivers branched from Donald Becker's vanilla driver
set, in the days before BitKeeper and git, a driver changelog was
maintained in the driver source code.  These days, the kernel's
changelog is far superior and much more accurate, so the in-driver
changelogs are removed.

Another relic of the Becker/kernel split was version numbering, using
"foo-LKx.y.z" notation, resulting in weird version numbers like
"1.17b-LK1.1.9".  These drivers are for older hardware, and see few
changes these days, so the version numbers were all bumped to something
more simple.

Finally, in xircom_tulip_cb specifically, an additional cleanup removes
the always-enabled CARDBUS cpp macro.
Signed-off-by: NJeff Garzik <jeff@garzik.org>
      03a8c661
  7. 03 7月, 2006 1 次提交
  9. 01 7月, 2006 1 次提交
  11. 28 6月, 2006 1 次提交
  13. 27 6月, 2006 1 次提交
    • J
      [netdrvr] Remove long-unused bits from Becker template drivers · 1f1bd5fc
      由 Jeff Garzik 提交于 
      Symbols such as PCI_USES_IO, PCI_ADDR0, etc. originated from Donald
Becker's net driver template, but have been long unused.  Remove.

In a few drivers, this allows the further eliminate of the pci_flags (or
just plain flags) member in the template driver probe structure.

Most of this logic is simply open-coded in most drivers, since it never
changes.

Made a few other cleanups while I was in there, too:
* constify, __devinitdata several PCI ID tables
* replace table terminating entries such as "{0,}," and "{NULL},"
  with a more-clean "{ }".
Signed-off-by: NJeff Garzik <jeff@garzik.org>
      1f1bd5fc
  15. 24 6月, 2006 1 次提交
  17. 20 6月, 2006 1 次提交
  19. 18 6月, 2006 1 次提交
    • H
      [NET]: Add netif_tx_lock · 932ff279
      由 Herbert Xu 提交于 
      Various drivers use xmit_lock internally to synchronise with their
transmission routines.  They do so without setting xmit_lock_owner.
This is fine as long as netpoll is not in use.

With netpoll it is possible for deadlocks to occur if xmit_lock_owner
isn't set.  This is because if a printk occurs while xmit_lock is held
and xmit_lock_owner is not set can cause netpoll to attempt to take
xmit_lock recursively.

While it is possible to resolve this by getting netpoll to use
trylock, it is suboptimal because netpoll's sole objective is to
maximise the chance of getting the printk out on the wire.  So
delaying or dropping the message is to be avoided as much as possible.

So the only alternative is to always set xmit_lock_owner.  The
following patch does this by introducing the netif_tx_lock family of
functions that take care of setting/unsetting xmit_lock_owner.

I renamed xmit_lock to _xmit_lock to indicate that it should not be
used directly.  I didn't provide irq versions of the netif_tx_lock
functions since xmit_lock is meant to be a BH-disabling lock.

This is pretty much a straight text substitution except for a small
bug fix in winbond.  It currently uses
netif_stop_queue/spin_unlock_wait to stop transmission.  This is
unsafe as an IRQ can potentially wake up the queue.  So it is safer to
use netif_tx_disable.

The hamradio bits used spin_lock_irq but it is unnecessary as
xmit_lock must never be taken in an IRQ handler.
Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      932ff279
  21. 27 5月, 2006 1 次提交
  23. 20 5月, 2006 1 次提交
  25. 29 3月, 2006 1 次提交
  27. 28 3月, 2006 1 次提交
  29. 23 3月, 2006 1 次提交
  31. 10 3月, 2006 2 次提交
  33. 07 2月, 2006 1 次提交
  35. 29 1月, 2006 1 次提交
  37. 27 1月, 2006 3 次提交
  39. 17 1月, 2006 1 次提交
  41. 13 1月, 2006 1 次提交
  43. 09 1月, 2006 1 次提交
  45. 29 10月, 2005 1 次提交
  47. 19 10月, 2005 1 次提交
  49. 04 10月, 2005 1 次提交
  51. 14 9月, 2005 1 次提交
  53. 11 9月, 2005 1 次提交
  55. 06 9月, 2005 1 次提交
  57. 31 8月, 2005 2 次提交
  59. 20 8月, 2005 1 次提交
  61. 12 8月, 2005 1 次提交
  63. 30 7月, 2005 1 次提交
    • P
      [netdrvr] add 'uli526x' driver (a tulip clone) · 4689ced9
      由 Peer Chen 提交于 
      We want to extract our LAN card driver from tulip core driver and
make a new file uli526x.c at tulip folder, because we have added
some ethtool interface support and non-eprom support in our driver
and may be other change in the futher.

If our controllers support are still contained in the tulip core
driver, I think it'll increase the complexity of maintenance, you
know, tulip core driver include several files and support so many
other controllers.  Furthermore, I tested the newest kernel 2.6.12
and I found the tulip driver can not work on our lan controller, and
I no time to debug it, so I aspired want to make a single uli526x.c
file just for our controllers.  Could you help us remove the ULi
m5261/m5263 lan controller support from tulip core driver and add
the new single uli526x.c file for us?
Signed-off-by: NPeer Chen <Peer.Chen@uli.com.tw>
Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      4689ced9
  65. 29 6月, 2005 1 次提交
    • D
      [NET]: Remove gratuitous use of skb->tail in network drivers. · 689be439
      由 David S. Miller 提交于 
      Many drivers use skb->tail unnecessarily.

In these situations, the code roughly looks like:

	dev = dev_alloc_skb(...);

	[optional] skb_reserve(skb, ...);

	... skb->tail ...

But even if the skb_reserve() happens, skb->data equals
skb->tail.  So it doesn't make any sense to use anything
other than skb->data in these cases.

Another case was the s2io.c driver directly mucking with
the skb->data and skb->tail pointers.  It really just wanted
to do an skb_reserve(), so that's what the code was changed
to do instead.

Another reason I'm making this change as it allows some SKB
cleanups I have planned simpler to merge.  In those cleanups,
skb->head, skb->tail, and skb->end pointers are removed, and
replaced with skb->head_room and skb->tail_room integers.
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
Acked-by: NJeff Garzik <jgarzik@pobox.com>
      689be439