Re: 2.6.7-mm1 PCNet Problems under VMWare 4.5.2

[Esteve Espuña Sargatal]

Aren't bits 31-16 of CSR0 reserved on PCnet-II (79c970A) ?

>From 79c970A Datasheet page 108:

CSR0:
[SNIP] The register is designed so that these indicator bits are cleared
by writing ONESs to those bit locations. This means that the software
can read CSR0 and write back the value just read to clear the interrupt
condition. [SNIP]

bits 31-16 Rserved. Written as ZEROs and read as undefined.
[SNIP]
bit 6 is IENA Interrupt Enable.


Thanks.


On Wed, 2004-06-23 at 11:23, Keith Moore wrote:
> I'm seeing problems running a 2.6.7-mm1 kernel with Fedora Core 2 
> running in a VMWare Workstation 4.5.2 VM. The kernel hangs trying to 
> bring up the (dhcp-enabled) eth0 interface.
> 
> I dug through the -mm1 patch, and the problem seems to be the changes at 
> the end of the pcnet32_interrupt() function (in drivers/net/pcnet32.c). 
> The relevant patch fragment is:
> 
> -    /* 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);
> 
> 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, writing 0x0140 instead of 0x0040 seems 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.
> 
> 
> KM
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/