Re: FA-311 / Natsemi problems with 2.4.1

Re: FA-311 / Natsemi problems with 2.4.1

[Jocelyn Mayer]

[-- Attachment #1: Type: text/plain, Size: 308 bytes --]

I found something from OpenBSD:
the natsemi chip (in fact DP83815)
is quite the same as SiS900 one.
You'll find as attachement the driver code
from OpenBSD.
If someone wo knows something about OpenBSD driver
could merge the driver drivers into Linux,
I think it would be a real great deal !

Jocelyn Mayer



[-- Attachment #2: openBSD-national.tgz --]
[-- Type: application/octet-stream, Size: 15126 bytes --]

Re: FA-311 / Natsemi problems with 2.4.1

[Jeff Garzik]

Jocelyn Mayer wrote:
> 
> I found something from OpenBSD:
> the natsemi chip (in fact DP83815)
> is quite the same as SiS900 one.

If that is true, maybe you can hack drivers/net/sis900.c to get it to
work with the FA-311?

	Jeff



-- 
Jeff Garzik       | "You see, in this world there's two kinds of
Building 1024     |  people, my friend: Those with loaded guns
MandrakeSoft      |  and those who dig. You dig."  --Blondie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: FA-311 / Natsemi problems with 2.4.1

[Ben Pharr]

At 05:28 PM 2/6/01 , you wrote:
>Jocelyn Mayer wrote:
> >
> > I found something from OpenBSD:
> > the natsemi chip (in fact DP83815)
> > is quite the same as SiS900 one.
>
>If that is true, maybe you can hack drivers/net/sis900.c to get it to
>work with the FA-311?
>
>         Jeff


My FA311 works fine with the natsemi driver.

Ben Pharr
bnpharr@olemiss.edu
-------------

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: FA-311 / Natsemi problems with 2.4.1

[Jocelyn Mayer]

/>>  /
/>> I found something from OpenBSD: /
/>> the natsemi chip (in fact DP83815) /
/>> is quite the same as SiS900 one. /

 > If that is true, maybe you can hack drivers/net/sis900.c to get it to
 > work with the FA-311?

 >       Jeff

First of all, I'm sorry to be so late to answer,
but we had problems with our mail server, last week (damned NT.....) :=(((

I know that some (maybe a lot..) of the FA311 cards work well with the 
natsemi driver.
I know that some doesn't work, also. In fact, I don't use a FA311 card,
but a DP83815 Chip included on a motherboard.
And, in my case, the driver fails....

I started to work on the SiS900 driver.
I will try to do something about it...
Maybe it won't be quick,
because I'm not used to work so deep inside the kernel,
but it's a good time to start ! :=)))

So, please be patient, I'll come back with something new,
one of these days...

Jocelyn Mayer.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

FA-311 / Natsemi problems with 2.4.1

[Tom Popowski]

Please CC me, as I don't follow the list.

Please also forgive me if I'm stepping on toes.  I'm in user-space.

I have had similar problems (network server XXXX not responding) with
both a Netgear FA311 (DP83815) and a Macronix (tulip) card when using
Donald Becker's drivers under 2.2.x  kernels when connected to a Netgear
FE108 (100BaseTx-HD) hub.  Both work correctly when dumbed-down to
10Mb.  The fa311 driver from Netgear worked fine at 100Mb with a 2.2
kernel.

Under 2.4.x, fa311 doesn't compile and natsemi.c gives the messages
below.  Again, I can (and do) force the card to 10Mb and it works fine
with the natsemi driver.

> I'm having problems with the natsemi drivers on my Netgear FA-311 card.
>
> On one host, I get lots of messages like this:
>
> eth1: Something Wicked happened! 0700.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0740.
> eth1: Something Wicked happened! 0540.
>
--
Tom Popowski
Software Support
Northwest Geophysical Associates, Inc.
http://www.nga.com


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: FA-311 / Natsemi problems with 2.4.1

[Jocelyn Mayer]

[-- Attachment #1: Type: text/plain, Size: 611 bytes --]

Well, I know this problem very well....

It seems that the original driver has some problems
to set up the chip and flush its receive buffers before
transmitting them.
I made some patches to make this chip work well.
I have one for 2.2.17 kernel, and one for 2.4.0 one.
I sent this patch to D. Becker some time ago,
but he never replied me, and, as far as I know,
never integrated it.

Here's my version for 2.2.17 kernel.
I made it work very well for a few weeks.
It's a bzip2 attachement,
as it is a bit long....
I'll send my patch for 2.4 kernel
as soon as I have finished to clean it up !!!

Jocelyn Mayer


[-- Attachment #2: natsemi.c.bz2 --]
[-- Type: application/octet-stream, Size: 13650 bytes --]

Re: FA-311 / Natsemi problems with 2.4.1

[Manfred Spraul]

Jocelyn Mayer wrote:
> 
> I'll send my patch for 2.4 kernel
> as soon as I have finished to clean it up !!!
>

A few points:

* set your tabs to 8, and indent by 8 characters.
* Nastemi_auto_negociate: remove the 'static' variable - what if someone
has multiple cards installed?
* You cannot wait for for more than a few dozend microseconds in an
hardware interrupt handle, and a few hundred microseconds in a bottom
half handler (e.g a timer)
Probably the autonegotiation takes longer - add a timer that calls you
back after 50 milliseconds, and return.

And are you sure that a full reset is required for a simple link change?

Most other drivers are written the other way around:
tx_timeout() performs the full reset if the transmitter is hung for > 2
seconds, and link_change only changes the chip configuration.


--
	Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

FA-311 / Natsemi problems with 2.4.1

[Misc Mail for Erich]

I'm having problems with the natsemi drivers on my Netgear FA-311 card.

On one host, I get lots of messages like this:

eth1: Something Wicked happened! 0700.
eth1: Something Wicked happened! 0740.
eth1: Something Wicked happened! 0740.
eth1: Something Wicked happened! 0740.
eth1: Something Wicked happened! 0740.
eth1: Something Wicked happened! 0740.
eth1: Something Wicked happened! 0540.

This is on a K6-166

On my athlon/duron, I don't get those messages, but once in a while it will 
just stop working.  If I bring the interface down, remove the module, and 
bring the interface back up again it will start to work again.

These two cards are connected by a crossover cable.  When the cards are 
working the link works just fine.

What more information do I need to obtain?  Please cc me, though I'll
be watching the list archives as well.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/