Now that I'm flattening out the SouthBridge object, I'm ending up breaking the solution I had before to allow the PC platform to program the initial state of the 8254 PIT. What would happen before was that the SouthBridge would tell the PC platform about itself, and then later the platform would get at the timer through the SouthBridge and configure it properly. Now there's no SouthBridge, and I don't want to push the artificial initial configuration code down into the device itself. One possible solution I was thinking of would be to actually just do functional accesses to the right locations to program the PIT like software would. I'm not sure that would work, though, since I don't know if all the devices have been constructed or hooked up to the memory system yet. Another option would be to record in the PC simobject where the timer is since the timer is created and hooked up by the python version. I don't necessarily want to make it a Param though, because I don't want anyone to be able to modify what it's pointing at. All the other connections, to the 8259 PIC, the speaker, etc, will all be to the original object, so it won't do any good for the C++ PC object to initialize something else. Any ideas?
Gabe _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
