Yes. It's the same setup that I mentioned in one of my
other posts (10baseT-HD to a cable modem). I'd like to
know if it fixes other peoples media selection problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=361391
That didn't work by itself. There are two other spots
where CSR13 is written to and not from that table:
diff -u linux-2.4.12/drivers/net/tulip/tulip_core.c
linux/drivers/net/tulip/tulip_core.c
--- linux-2.4.12/drivers/net/tulip/tulip_core.c Tue Oct 2
12:00:58 2001
+++ linux/drivers/net/tulip/tulip_core.c Sun Oct 28
13:40:24 2001
@@ -403,7 +403,7 @@
if (tp->sym_advertise & 0x0040)
tp->csr6 |= FullDuplex;
outl(tp->csr6, ioaddr + CSR6);
- outl(0x0000EF01, ioaddr + CSR13);
+ outl(0x0000EF05, ioaddr + CSR13);
} else if (tp->chip_id == DC21142) {
if (tp->mii_cnt) {
@@ -1706,7 +1706,7 @@
outl(0xFFFFFFFF, ioaddr + CSR14);
outl(0x00000008, ioaddr + CSR15); /* Listen
on AUI also. */
outl(inl(ioaddr + CSR6) | csr6_fd, ioaddr +
CSR6);
- outl(0x0000EF01, ioaddr + CSR13);
+ outl(0x0000EF05, ioaddr + CSR13);
break;
case DC21040:
outl(0x00000000, ioaddr + CSR13);
Logged In: YES
user_id=17443
So... with my patch -plus- your patch here, 2.4.x tulip
works?
Logged In: YES
user_id=361391
Yes. It's the same setup that I mentioned in one of my
other posts (10baseT-HD to a cable modem). I'd like to
know if it fixes other peoples media selection problems.