-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Processor class #242
Comments
The only thing Processor class could be used to is the mapping between virtual id, physical id and possibly for spin 2 coreY and coreX Currently the Chip class already holds the virtual to physical mapping. |
Chip would just keep a list of scamp/monitor and user/none_scamp (Virtual) ids. |
If and when we need to include information on Processor Quads I still don't think the Processor class will help. |
farther examination shows the only place Processor class is used is in a unit test to use it as part of a vertex label |
Fixed by #246 |
The processors are indexed by ID in chip
With #237 the scamp(monitor) cores are kept separate from the "user" or none scamp ones.
So Processor.is_monitor is no longer used.
Processor methods dtcm_available, cpu_cycles_availabe and clock_speed return constant values.
Better to move these values to Version when and if anything cares!
The text was updated successfully, but these errors were encountered: