> Your platform code or BIOS is buggy. PPC people had a similar problem. > Zero is not currently taken as "unallocated" by the PCI layer and, while > Linus suggested it could be, Dave Woodhouse and others pointed out there > are systems which legitimately use address 0 on the PCI in this way. The claim from the BIOS team is that on this system only legacy mode is supported (indicated by the Class Code Programming model being 0x8A) and since drivers/utilities should not make assumptions about these BAR values when the device is in legacy mode, they don't have to initialize them. The BARS would only be guaranteed to be set when programming model 0x8F (native mode) is set. Which sounds sort of plausible ... but perhaps that's because I have not idea what a "Class code programming model" is. Does that make any sense? > Sounds like you need to fix up after your firmware in your boot code, > perhaps with an arch specific pci header quirk. If many other BIOS writers believe the same thing as ours, then maybe it might be worth fixing ... otherwise it looks like we'll need a quirk (this machine is old, there isn't much liklihood of an updated BIOS release for just this issue). -Tony - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
