Hi,
and Martins patch:
This one works standalone and with 2 and 3 above. It seems to have
increase ftp transfer rates too from 8600Kbytes/sec to 10577Kbytes/sec.
Cool.
Ofcourse, for some odd reason, if the ftp was done from a Windows XP Pro
machine, it's only 6722KBytes/sec.
Hmm.
Hi,
1) dc driver uses wrong case to read MAC from eeprom.
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482
This one seems to break data sending/receiving as the only thing that
works is pinging and that's only on the alias/secondary IP and not the
primary IP network which is
On Tue, 10 Sep 2002, Martin Blapp wrote:
Hi,
1) dc driver uses wrong case to read MAC from eeprom.
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482
This one seems to break data sending/receiving as the only thing that
works is pinging and that's only on the alias/secondary IP
Hi Martin:
On Tue, 10 Sep 2002, Martin Blapp wrote:
and Martins patch:
This one works standalone and with 2 and 3 above. It seems to have
increase ftp transfer rates too from 8600Kbytes/sec to 10577Kbytes/sec.
Cool.
Seems to depend on which notebook the card is in. With the
On Wednesday, 4th September 2002, Martin Blapp wrote:
And this patch here together with patch III made the annoying messages (dc0:
failed to force tx and rx to idle mode) go away. And I can use now my card
without to replug the cable over again)
I've been meaning to remove the annoying message
On Mon, Sep 09, 2002 at 11:59:08PM +1000, Stephen McKay wrote:
This driver represents a counterintuitive state of affairs. I was impressed
when Bill Paul managed to support so many clone cards with one driver. But
now nobody has enough hardware on hand to test any change properly. There's
On Thu, 5 Sep 2002, Martin Blapp wrote:
When I tried these patches manually handpatching on 08182002 JP
SNAPSHOT, it took away the error messages like you had mentioned except
I can ping everything except for the gateway. Also, no other protocols
would work at all so it seems like
On Wed, 4 Sep 2002, Martin Blapp wrote:
Hi all,
Anybody who can, please commit these PR's.
1) dc driver uses wrong case to read MAC from eeprom.
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482
2) Tulip ether card EN2242 (if_dc.c) use wrong multicast table
Hi,
When I tried these patches manually handpatching on 08182002 JP
SNAPSHOT, it took away the error messages like you had mentioned except
I can ping everything except for the gateway. Also, no other protocols
would work at all so it seems like something else broke. I took out
the
On Thu, 5 Sep 2002, Martin Blapp wrote:
Hi,
When I tried these patches manually handpatching on 08182002 JP
SNAPSHOT, it took away the error messages like you had mentioned except
I can ping everything except for the gateway. Also, no other protocols
would work at all so it seems
Hi all,
Anybody who can, please commit these PR's.
1) dc driver uses wrong case to read MAC from eeprom.
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/35482
2) Tulip ether card EN2242 (if_dc.c) use wrong multicast table
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=misc/32699
3) ADMtek
Ups, forgot to add here the PR number ...
3) ADMtek AN98x, enable automatically TX underrun recovery
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34236
Patch No3 fixes some part of link problem on EN2242 cards.
I've tested this patch and it makes by laptop working again with
cvsup.
Martin
OK, I've grabbed these...
M
Ups, forgot to add here the PR number ...
3) ADMtek AN98x, enable automatically TX underrun recovery
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34236
Patch No3 fixes some part of link problem on EN2242 cards.
I've tested this patch and it makes by
13 matches
Mail list logo
