RE: [PATCH 1/1] r8169.c correct MSIEnable register offset

[hayeswang]

> -----Original Message-----
> From: David Miller [mailto:davem@xxxxxxxxxxxxx] 
> Sent: Thursday, December 15, 2011 2:44 PM
> To: romieu@xxxxxxxxxxxxx
> Cc: cantona@xxxxxxxxxxxxxxxxx; Hayeswang; 
> linux-kernel@xxxxxxxxxxxxxxx; nic_swsd; netdev@xxxxxxxxxxxxxxx
> Subject: Re: [PATCH 1/1] r8169.c correct MSIEnable register offset
> 
> From: Francois Romieu <romieu@xxxxxxxxxxxxx>
> Date: Wed, 14 Dec 2011 22:37:13 +0100
> 
> > Su Kang Yin <cantona@xxxxxxxxxxxxxxxxx> :
> >> correct MSIEnable (bit 5) register to Config1 (offset 
> 0x52) instead of
> >> Config2 (offset 0x53)
> > 

The bit 5 of config1 (0x52) is reserved. And the bit 5 of Config2 (0x53) is
MSIEnable only for 8169 controler series.

> > I wonder where the inspiration for the MSIEnable bit came from.
> > It looks like something was confused with the Message Control word
> > in PCI space.
> > 
> > Imho you can simply remove it altogether.
> 
> Someone should find out what the real situation is with this.
> 
> Maybe it mirrors the PCI config space setting and is read-only, maybe
> not.  But it should be determined for sure before changing this. :-)
> 

--
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/