Error accessing PCI config space
mlan at mcp.cpu.lu
Tue Nov 23 12:39:25 EST 1999
> On Tue, Nov 23, 1999, Michel Lanners <mlan at cpu.lu> wrote:
> >The error is that whenever I read from config space, I get the value of
> >the previous read, however long ago that read occured. See this:
> Could you try reading back the config address before actually reading the
> value ? That's how I got the uni-north config space accesses to work.
Actually I've tried that (it's hinted at in some Apple documentation
as the only way to make sure a PCI posted write has completed); however,
I'm only getting garbage in that case. Or maybe I didn't look hard enough
at the garbage to identify it ;-)
> Also, there was a weird thing about the data location that had to be
> offseted by modulo 8. If Apple used the same bits of ASIC design for it,
> then it may work. (Look at the uni-n code in my iBook patches).
OK, I'll take a look at that when I'm back at home tonight. I'll also
try whether older kernels didn't work correctly in thsi respect; maybe
something in the system setup changed and broke this specific PCI access.
On a related note, the PCI bus scanning code in drivers/pci/pci.c seems
to get at least part of the config space right; as it gets vendor and
device ID ok. I'll investigate...
.signature at home
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-dev