Aaron Durbin wrote:
Compare with how HT (doesn't) works, or with PCI.
What is an impressive implementation for sending messages to ports? It's just another address space through index/data pairs.
That's exactly what I disagree with. There is an architecture and I would expect coreboot to model it rather than dumping an array of magic number pairs into index/data.
The coreboot devicetree doesn't model HT so well - it is treated as "another address space". I think it would be better to avoid repeating such a mistake?
//Peter
This is all pretty nebulous. I can't understand the point here.
docs or code would help.
ron
On Tue, Feb 18, 2014 at 10:11 AM, Peter Stuge peter@stuge.se wrote:
In what way? Something that is probe-able? And something that isn't?
What is it that you are suggesting/wanting devicetree to do what in this case? I am failing to understand the mistake you are referring to. Could you please provide explicit examples having c struct fields represented in devicetree that model another address space?
-Aaron