Yes. I'll do that.
Ali Saidi wrote:
You can look at how this is done in the tsunami classes. Each one of
the Tsunami children (Tsunami I/O, Tsunami PChip, Tsunami CChip), sets
a pointer back in the Tsunami object at in the constructor. While this
isn't available in the Constructor of the Tsunami instruction it is
available in the init() function since object construction has all
happened then. You can then set the timer as appropriate in init()
from the platform.
Make Sense?
Ali
On May 31, 2008, at 3:29 PM, Flyspray wrote:
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this: - Gabe Black (gblack)
Attached to Project - M5 Bugs
Summary - Move timer 0 initialization out of timer object
Task Type - Minor Enhancement
Category - Device Models
Status - New
Assigned To - Gabe Black
Operating System - All
Severity - Low
Priority - Normal
Reported Version - 2.0beta5
Due in Version - 2.1
Due Date - Undecided
Details - In x86 the BIOS would normally initialize timer 0, but since
we don't have a BIOS right now that has to happen elsewhere. Ideally
it should be in the platform object, but the C++ platform object, PC,
can't have a parameter giving it access to the timer because that
creates a cycle in the object tree. Having a "real" BIOS would allow
getting rid of this code all together which would be ideal.
More information can be found at the following URL:
http://www.m5sim.org/flyspray/task/316
You are receiving this message because you have requested it from the
Flyspray bugtracking system. You can be removed from future
notifications by visiting the URL shown above.
_______________________________________________
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
