I would look at the kernel and see exactly what it's trying to probe and start with just returning the values it expects and see how far that gets you (The ISAFake device is especailly useful for this sort of thing). I imagine there is something more generic, but the kernel source will probably tell you that. If it does something to guess the chipset and then has a custom probing routine for each than maybe not, but I bet it's pretty standard and you can likely just return the values it expects with the ISAFake device, especially if it's only used for this probing and then forgotten about.
Ali On Jun 9, 2008, at 2:04 PM, Gabe Black wrote: > So this would be the PCI bus support in the north bridge for instance? > Should I just arbitrarily pick a chipset and implement that, or is > there > something more generic? > > Gabe > > nathan binkert wrote: >>> So as it says, it's checking bus 0 device 0 for a host bridge. Do we >>> have a way to set that up? I can short circuit that by filling in >>> one of >>> the tables from the BIOS a little more, but if this is something I'm >>> going to need to do anyway I'd rather do that. >> >> I believe that bus 0 is on the host bridge device. You're going to >> need to create a new device so that the PCI bus can be discovered. >> It >> shouldn't be complicated since there aren't that many registers >> involved. I'm not sure how complicated the linux code is for this >> stuff, but the BSD code isn't too bad. >> >> Nate >> _______________________________________________ >> m5-dev mailing list >> [email protected] >> http://m5sim.org/mailman/listinfo/m5-dev > > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
