On 3 June 2014 03:06, Peter Crosthwaite <[email protected]> wrote: > This series is work-in-progress and has numerous FIXMEs in it. > Looking for conceptual level commentary
Looks good and like the right thing to me. To check I understand how the QOM stuff is working here, for a transaction master we expose an MR link property, which the board sets to be a pointer to some appropriate MR (which is owned by the board). Conversely, for a transaction slave (ie a device), the device owns its own memory regions. The board can map those via the traditional APIs for putting MRs in containers, or it could choose to set the MR 'container' link property to point at the container MR (plus the addr property). The transaction master properties/API actually make much more sense to me than the slave ones... thanks -- PMM
