qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v1 0/6] Cleanup of ARM MPCore


From: Peter Crosthwaite
Subject: Re: [Qemu-devel] [PATCH v1 0/6] Cleanup of ARM MPCore
Date: Tue, 19 Feb 2013 10:52:16 +1000

On Tue, Feb 19, 2013 at 4:53 AM, Peter Maydell <address@hidden> wrote:
> On 8 February 2013 04:03, Peter Crosthwaite
> <address@hidden> wrote:
>> Patches 1-3 and 5 are trivial code cleanup and may be candidate to go
>> via trivial queue inpdependent of review of this work. Patch 4 unifies
>> the MPTimer and WDT into one device. My motivation for doing this is
>> so I can dynamically create one without the other (Im throwing away
>> MPCore altogether in one of my flows and creating these components
>> individually).
>
> Generally I like these patches, but I'm curious about what your use
> case is where you don't just create an entire a9mpcore.

Automatic machine model creation from my CAD tool outputs. My CAD
tools itemize each of the MPCore components separately and has no
sense of an MPCore, so my machine creation mechanism wants to see each
of these individually. Otherwise i would need to preprocess that AD
output to identify the flattened collection of components as an
MPCore.

 That qdev
> object is intended to encapsulate the equivalent bit of hardware,
> so if you need to create the subcomponents individually then either
> your hardware is really odd or maybe we need to make the container
> a little more flexible...
>
>> P.S. I am aware of the email threading issue and am working on it.
>
> Appreciated -- I'm moving over to using Anthony's patches script
> now and it can't cope with the unthreaded versions, so I have to
> manually download them all from patchwork instead.
>

Resolved.

Regards,
Peter

> thanks
> -- PMM
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]