![]() | |||||||||||
Messages in this thread |
On Mon, Apr 12, 2004 at 08:28:01AM +0100, Russell King wrote: > > > 3) FOR FURTHER INVESTIGATION: Does linux hdsp driver force the f0 > > value upon the 0x81 register or is it that in Linux one simply > > cannot select d0 value for whatever reason > > I suspect it may be caused by using a byte access to a longword-sized > register. 0x81 is supposed to be accessed via: > > setpci -s a.0 0x80.l > > which of course means its bits 8 to 15. I don't think so; I'm not sure what the PCI spec has to say about it, but I have not had problems doing byte reads/writes for longer PCI configuration registers. Bit 9 of the sysctl register for the TI 1410 is "socket activity"; it is read only and is cleared after each read. The key change is setting bit 14 (enable upstream burst reads). Regarding the register at 0xc9, I don't think that is defined in any TI bridge data sheet; it is in a "reserved" range. -- Dave - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2005-03-22 14:02 [from the cache] ©2003-2008 | |||||||||||