linux-toradex.git/drivers/net/sky2.c, branch v2.6.19.2

[PATCH] sky2: netpoll on dual port cards

2006-11-01T01:22:06+00:00

The sky2 driver uses a single NAPI poll routine for both ports on dual ported
cards (because there is a single IRQ and status ring). Netpoll makes assumptions
about the relationship between network device and NAPI that aren't correct
on the second port, this will cause the port to never clear work.

Most systems, just have single port, so not a big issue.
The easy fix is just make the second port, not netpoll capable.

Signed-off-by: Stephen Hemminger 
Signed-off-by: Jeff Garzik

[PATCH] skge, sky2, et all. gplv2 only

2006-11-01T01:22:06+00:00

I don't want my code to downgraded to GPLv3 because of
cut-n-pasted the comments. These files which I hold copyright
on were started before it was clear what GPLv3 was going to be.

Signed-off-by: Stephen Hemminger 
Signed-off-by: Jeff Garzik

[PATCH] sky2: 88E803X transmit lockup

2006-10-21T18:08:24+00:00

The reason sky2 driver was locking up on transmit on the Yukon-FE chipset
is that it was misconfiguring the internal RAM buffer so the transmitter
and receiver were sharing the same space.

The code assumed there was 16K of RAM on Yukon-FE (taken from vendor driver
sk98lin which is even more f*cked up on this). Then it assigned based on that.
The giveaway was that the registers would only hold 9bits so both RX/TX
had 0..1ff for space. It is a wonder it worked at all!

This patch addresses this, and fixes an easily reproducible hang on Transmit.
Only the Yukon-FE chip is Marvell 88E803X (10/100 only) are affected.

Signed-off-by: Stephen Hemminger 
Signed-off-by: Jeff Garzik

sky2: accept multicast pause frames

2006-10-17T17:24:23+00:00

When using flow control, the PHY needs to accept multicast pause frames.
Without this fix, these frames were getting discarded by the PHY before
doing any flow control.

Signed-off-by: Stephen Hemminger

sky2: version 1.9

2006-10-17T17:24:18+00:00

Mark version, this has been a lot of patches.

Signed-off-by: Stephen Hemminger

sky2: no message on rx fifo overflow

2006-10-17T17:24:16+00:00

Under high load it is possible to make the receiver FIFO get overloaded.
The driver/hardware recover properly, so there is no reason to fill the log
with lots of extra messages, just update counter.

Signed-off-by: Stephen Hemminger

sky2: flow control setting fixes

2006-10-17T17:24:13+00:00

The result of flow control negotiation should not limit the next
negotiatition. If board is plugged into an old half duplex 10Mbit port,
without pause, then replugged into a gigabit port, it should negotiate
what is desired, not inherit that last negotiation.

Signed-off-by: Stephen Hemminger

sky2: don't reset PHY twice

2006-10-17T17:24:10+00:00

Don't need to reset PHY twice on startup.

Signed-off-by: Stephen Hemminger

sky2: use duplex result bits

2006-10-17T17:24:08+00:00

The result of duplex negotiation is avaliable in the phy status
register, so use that to simplify code and avoid rereading the PHY.

Signed-off-by: Stephen Hemminger

sky2: fiber pause bits

2006-10-17T17:24:04+00:00

The advertisement bits for flow control are located in
different location on fiber (1000baseX)

Signed-off-by: Stephen Hemminger