2.6.7-mm1 PCNet Problems under VMWare 4.5.2
Quoted 5 lines · Keith Moore
(quoted diff) +2
-2- /* Clear any other interrupt, and set interrupt enable. */ - lp->a.write_csr (ioaddr, 0, 0x7940); + /* Set interrupt enable. */ + lp->a.write_csr (ioaddr, 0, 0x0040);
Quoted 8 lines
Reverting this one section of the patch makes eth0 happy again.
I poked around with the values written to the csr register, and it appears the virtual PCNet-II adapter needs bit
0x0100(initialzation done) set. So, writing0x0140instead of0x0040seems to work well.I have no idea how accurate VMWare's emulation of this adapter is, or if this change may cause problems with other (physical) adapters.
I believe that it is not emulation bug. What happens is that you do not confirm INIT DONE irq, causing endless stream of interrupts from card to the CPU. This happens because CSR3 default value is 0 (enable all interrupts), and driver does not modify it in any way (f.e. for preventing INIT from causing interrupt). So when init is done, IDON irq fires. In old driver it was acked by 0x7940 (or by 0x0140 in your modified driver), but in new driver it is not acked in any way, triggering this very same IRQ over and over.
pcnet32_interrupt should loop while csr0 contains some pending interrupts (current mask 0x8600 should be changed to 0xDE00 to be 100% sure that all interrupts we handle in loop are catched), and then clear all other interrupts sources (0x2140) out of the loop.
Other possibility is masking these unused sources in CSR3...
But I believe that driver from -mm1 will hang even on real Am79C970A hardware.
Best regards,
Petr Vandrovec