* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/50.memtest/alpha/linux/memtest passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/sim
This is more or less what I was suggesting. Everything can be a first
class SimObject, and all of the devices can attach to the bus, and the
SouthBridge C++ object can do all of the proper pointer setup and
device initialization.
Nate
> Why not have an keep the SouthBridge in the hierarchy to
Why not have an keep the SouthBridge in the hierarchy to manage the
pieces while having them all directly connect to the bus. This seems
like a lot of work to get rid of a SimObject in C++ that won't be
doing much.
Ali
On Aug 21, 2008, at 4:46 PM, [EMAIL PROTECTED] wrote:
> I don't think t
I don't think there's anything wrong with the southbridge as a conceptual
object, but I thought having it in the SimObject hierarchy was a bad idea
since, for instance in ancient PCs, all the little bits and pieces we're
dealing with were their own entities. It's conceivable that in the future thes
What was wrong with the southbridge object? Was it because of the
subdevice thing? I don't think you need to necessarily get rid of the
southbridge, you can still have it to do the initialization that you
want, I just think you want to make all of the things that were
subdevices proper SimObjects
The problem here isn't the memory locations things are attached at, it's doing
some initial configuration on the 8254 which I believe the BIOS would normally
do. If you look in the PC init function you can see where this is happening
currently. The southBridge pointer (I think) is near the top and
I'm not exactly clear what you're saying here. You had a SouthBridge
object, and in south_bridge.cc, it looks like you manually set the
memory locations of the various objects in the south bridge. Now, you
want to make the individual objects normal SimObjects, but you're
having trouble figuring o