linux.git/drivers/net/pcnet32.c, branch v2.6.25

pcnet32: Use print_mac

2008-02-11T15:28:31+00:00

Signed-off-by: Joe Perches 
Acked-by:  Don Fry 
Signed-off-by: Jeff Garzik

pcnet32: use NET_IP_ALIGN instead of 2

2008-02-11T15:28:30+00:00

Change hard coded 2 to NET_IP_ALIGN.  Added new #define with comments.
Tested amd_64

Signed-off-by:  Don Fry 
Signed-off-by: Jeff Garzik

netdev: use ARRAY_SIZE() instead of sizeof(array) / ETH_GSTRING_LEN

2008-01-28T23:03:36+00:00

Using ARRAY_SIZE() on arrays of the form array[][K] makes it unnecessary
to know the value of K when checking its size.

Signed-off-by: Alejandro Martinez Ruiz 
Signed-off-by: Jeff Garzik

[NET]: Fix drivers to handle napi_disable() disabling interrupts.

2008-01-09T07:30:12+00:00

When we add the generic napi_disable_pending() breakout
logic to net_rx_action() it means that napi_disable()
can cause NAPI poll interrupt events to be disabled.

And this is exactly what we want.  If a napi_disable()
is pending, and we are looping in the ->poll(), we want
->poll() event interrupts to stay disabled and we want
to complete the NAPI poll ASAP.

When ->poll() break out during device down was being handled on a
per-driver basis, often these drivers would turn interrupts back on
when '!netif_running()' was detected.

And this would just cause a reschedule of the NAPI ->poll() in the
interrupt handler before the napi_disable() could get in there and
grab the NAPI_STATE_SCHED bit.

The vast majority of drivers don't care if napi_disable() might have
the side effect of disabling NAPI ->poll() event interrupts.  In all
such cases, when a napi_disable() is performed, the driver just
disabled interrupts or is about to.

However there were three exceptions to this in PCNET32, R8169, and
SKY2.  To fix those cases, at the subsequent napi_enable() points, I
added code to ensure that the ->poll() interrupt events are enabled in
the hardware.

Signed-off-by: David S. Miller 
Acked-by:  Don Fry

pcnet32: remove private net_device_stats structure

2007-10-18T00:23:30+00:00

Remove the statistics from the private structure.
Use the net_device_stats in netn_device structure.

Following Jeff Garzik's massive cleanup Sep 01.
pcnet32 was not "low-hanging fruit".

Tested x86_64.

Signed-off-by:  Don Fry 
Signed-off-by: Jeff Garzik

pcnet32: remove compile warnings in non-napi mode

2007-10-18T00:17:34+00:00

Remove compile warning when in non-napi mode.

Signed-off-by:  Don Fry 
Signed-off-by: Jeff Garzik

pcnet32: fix non-napi packet reception

2007-10-18T00:17:34+00:00

Recent changes to the driver for the new napi API broke the reception
of packets when in non-napi mode.  The initialization of napi.weight
was removed for the non-napi case leaving the value zero.

Tested NAPI and non-NAPI on x86_64.

Signed-off-by: Don Fry 
Signed-off-by: Jeff Garzik

pcnet32: endianness

2007-10-10T23:52:01+00:00

Signed-off-by: Al Viro 
Signed-off-by: Jeff Garzik

[netdrvr] Stop using legacy hooks ->self_test_count, ->get_stats_count

2007-10-10T23:51:45+00:00

These have been superceded by the new ->get_sset_count() hook.

Signed-off-by: Jeff Garzik 
Signed-off-by: David S. Miller

[ETHTOOL] Provide default behaviors for a few ethtool sub-ioctls

2007-10-10T23:51:17+00:00

For the operations
	get-tx-csum
	get-sg
	get-tso
	get-ufo
the default ethtool_op_xxx behavior is fine for all drivers, so we
permit op==NULL to imply the default behavior.

This provides a more uniform behavior across all drivers, eliminating
ethtool(8) "ioctl not supported" errors on older drivers that had
not been updated for the latest sub-ioctls.

The ethtool_op_xxx() functions are left exported, in case anyone
wishes to call them directly from a driver-private implementation --
a not-uncommon case.  Should an ethtool_op_xxx() helper remain unused
for a while, except by net/core/ethtool.c, we can un-export it at a
later date.

[ Resolved conflicts with set/get value ethtool patch... -DaveM ]

Signed-off-by: Jeff Garzik 
Signed-off-by: David S. Miller