On Wed, Oct 24, 2012 at 10:42:55AM +0200, Markus Armbruster wrote:
> Peter Maydell writes:
>
> > A lot of the ARM board models follow the pattern of having a
> > single common init function which is called with various
> > parameters from the QEMUMachine init function for several board
> > model
Peter Maydell writes:
> On 24 October 2012 09:42, Markus Armbruster wrote:
>> Peter Maydell writes:
>>
>>> A lot of the ARM board models follow the pattern of having a
>>> single common init function which is called with various
>>> parameters from the QEMUMachine init function for several boar
On 24 October 2012 09:42, Markus Armbruster wrote:
> Peter Maydell writes:
>
>> A lot of the ARM board models follow the pattern of having a
>> single common init function which is called with various
>> parameters from the QEMUMachine init function for several board
>> model variants. The change
Peter Maydell writes:
> A lot of the ARM board models follow the pattern of having a
> single common init function which is called with various
> parameters from the QEMUMachine init function for several board
> model variants. The change to QEMUMachineInitArgs in commit 5f072e
> took the fairly
A lot of the ARM board models follow the pattern of having a
single common init function which is called with various
parameters from the QEMUMachine init function for several board
model variants. The change to QEMUMachineInitArgs in commit 5f072e
took the fairly mechanical approach of splitting t
