I already did number 1, I was trying to be diligent and make sure either
I didn't need to fake the device, which didn't sound like the case from
the previous emails, or that I had something in place without 1 that
worked properly. I'll just leave 1 in place and worry about other things
for now.
Looking at this code it seems like the easiest thing is to make sure
that dmi_get_year(DMI_BIOS_DATE) >= 2001.Do you have a DMI table? If
you set the BIOS date > 2001 the function could be skipped. It's just
checking if it some device exists that makes it think this is actually
PCI that it'
The code following the comment in my original email is below. Basically,
it looks like the kernel reads some registers out of the config space of
bus 0 dev 0 function 0-0x100 and sees if they match certain values. I'd
imagine that wouldn't be very hard to do but I don't have any experience
with the
> 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?
I think that there's really only one interface for this that really
matters. On alpha, there were lots of north bridge inte
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 prob
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?
> 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 h
Instead of plowing ahead with interrupts and all that stuff while I
don't have a lot of time to focus on it and the repository is in flux,
I've been going back over the part of the simulation that executes
already and cleaning up stuff I ignored at first. One thing is that the
kernel is con
