[239] in linux-net channel archive
Re: Packet-length patch to lance.c in 1.2.5?
daemon@ATHENA.MIT.EDU (Dave Platt)
Thu Apr 27 15:28:59 1995
Date: Thu, 27 Apr 95 10:45:52 PDT
From: dplatt@3do.com (Dave Platt)
To: linux-net@vger.rutgers.edu
> No, this is a PC-Net/ISA, 79C960.
Hmmm....
> Mmmmm, maybe that's what's supposed to happen, but it doesn't work
> that way. The FCS gets included.
This is odd...
> I don't see where it sets the strip
> pad and FCS bit in CSR4, not in 1.2.1.
/* Re-initialize the LANCE, and start it when done. */
outw(0x0001, ioaddr+LANCE_ADDR);
outw((short) (int) &lp->init_block, ioaddr+LANCE_DATA);
outw(0x0002, ioaddr+LANCE_ADDR);
outw(((int)&lp->init_block) >> 16, ioaddr+LANCE_DATA);
outw(0x0004, ioaddr+LANCE_ADDR);
outw(0x0d15, ioaddr+LANCE_DATA); /*** <---- here ***/
outw(0x0000, ioaddr+LANCE_ADDR);
outw(0x0001, ioaddr+LANCE_DATA);
This looks to me as if this sets CSR4 up with APAD_XMT, ASTRIP_RCV, MFCOM,
RCVCCOM, TXSTRTM, and JABM. I.e., it enabled auto-padding during
transmission, auto-stripping of pad and FCS during reception, and masks off
a bunch of interrupts. Am I misreading this?
> Only if it works! :)
I guess this is going to take some additional testing and investigation.
