This version of the natsemi driver is being successfully used by us (Myrio
Corporation) on hardware that has the 83815 chip on the motherboard, with
the 2.2.17 kernel. It appears to work well with both multicast and unicast,
with decent throughput. It requires the "pci-scan" module by Donald Becker
at scyld.com.
We would be very interested in any feedback on problems with 2.2.17 or
2.2.19, and our hope is that some experienced kernel developers will examine
it and alert us of potential problems we haven't tripped over yet.
Most of the code in this driver is by Donald Becker, of course. However, the
driver from scyld.com could not receive packets on our hardware. We started
from the modified version posted by Jocelyn Mayer. That one sort of worked
for us but had problems. Our version backed out some of those changes, and
has fixes for CRC calculation, reading the MAC address from the EEPROM, and
other things.
I (Torrey Hoffman) am not the developer of our version, although I did go
through it and clean it up a little. I am the alleged "Linux expert" here,
and if there are problems with the driver I am the person to contact.
I'm cc'ing everyone on my "natsemi" address list, please trim followups.
I do read the mailing list, but please cc me if responding.
Thanks.
Torrey Hoffman
[email protected]
[email protected]
On Wed, Apr 18, 2001 at 01:48:40PM -0700, Torrey Hoffman wrote:
>
> This version of the natsemi driver is being successfully used by us (Myrio
> Corporation) on hardware that has the 83815 chip on the motherboard, with
> the 2.2.17 kernel. It appears to work well with both multicast and unicast,
> with decent throughput. It requires the "pci-scan" module by Donald Becker
> at scyld.com.
>
> We would be very interested in any feedback on problems with 2.2.17 or
> 2.2.19, and our hope is that some experienced kernel developers will examine
> it and alert us of potential problems we haven't tripped over yet.
Well, on kernel 2.2.19 on a 'regular' PC box (celeron 533), it works
better than the 1.07b version from scyld.com, but it still gets tripped up
pretty bad by nfs traffic. (Have you tried NFS on your board at all?). It
seems to be acting a lot like the 2.4 driver does. (it seems to at least
recover from the error, whereas the scyld.com natsemi.c would appear to
not transmit any packets at all after having trouble).
I'm getting errors in RX packets..
RX packets:1959 errors:111 dropped:0 overruns:0 frame:305
TX packets:2275 errors:1 dropped:0 overruns:1 carrier:1
If anyone wants the dmesg output of this problem when running with
'debug=7', please let me know.
> Most of the code in this driver is by Donald Becker, of course. However, the
> driver from scyld.com could not receive packets on our hardware. We started
> from the modified version posted by Jocelyn Mayer. That one sort of worked
> for us but had problems. Our version backed out some of those changes, and
> has fixes for CRC calculation, reading the MAC address from the EEPROM, and
> other things.
>
> I (Torrey Hoffman) am not the developer of our version, although I did go
> through it and clean it up a little. I am the alleged "Linux expert" here,
> and if there are problems with the driver I am the person to contact.
>
> I'm cc'ing everyone on my "natsemi" address list, please trim followups.
> I do read the mailing list, but please cc me if responding.
>
> Thanks.
>
> Torrey Hoffman
> [email protected]
> [email protected]
>
>
>
--
Troy Benjegerdes | master of mispeeling | 'da hozer' | [email protected]
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's
why I draw cartoons. It's my life." -- Charles Shulz
On Wed, 18 Apr 2001, TroyBenjegerdes wrote:
> Well, on kernel 2.2.19 on a 'regular' PC box (celeron 533), it works
> better than the 1.07b version from scyld.com, but it still gets tripped up
> pretty bad by nfs traffic. (Have you tried NFS on your board at all?). It
Not tried NFS yet... Although, using the patch that I posted, everything
seems to work ok and then occasionally I get a big slow down - I haven't
had time to look to see what this is (it may even be something completely
unrelated like the kernel flushing buffers to disk)... I'll hopefully
test it sometime this week.
--
- Steve Hill
System Administrator Email: [email protected]
Navaho Technologies Ltd. Tel: +44-870-7034015
... Alcohol and calculus don't mix - Don't drink and derive! ...