As, in a very clear way, evidenced from the previous versions of this series, this series real goal was not not to create some new "malta-strict" machine, but to prepare path to creation of some imagined "malta-unleashed" machine which will, to the contrary of proclaimed goal, create a machine that could never exist in reality. That is why I can't accept this series.
Regards, Aleksandar уто, 30. јун 2020. у 21:58 Philippe Mathieu-Daudé <f4...@amsat.org> је написао/ла: > > Hi, > > This series add a new 'malta-strict' machine, that aims to properly > model the real hardware (which is not what the current 'malta' > machine models). > > Since v2: > - Initialize missing malta_machine_types::class_size > - Remove RFC patch that confuses Aleksandar > - Added examples of 'malta-strict' use > > $ git backport-diff -u v2 > Key: > [----] : patches are identical > [####] : number of functional differences between upstream/downstream patch > [down] : patch is downstream-only > The flags [FC] indicate (F)unctional and (C)ontextual differences, > respectively > > 001/5:[----] [--] 'hw/mips/malta: Trivial code movement' > 002/5:[----] [--] 'hw/mips/malta: Register the machine as a TypeInfo' > 003/5:[0001] [FC] 'hw/mips/malta: Introduce MaltaMachineClass::max_ramsize' > 004/5:[----] [--] 'hw/mips/malta: Introduce the 'malta-strict' machine' > 005/5:[----] [--] 'hw/mips/malta: Verify malta-strict machine uses correct > DIMM sizes' > > Philippe Mathieu-Daudé (5): > hw/mips/malta: Trivial code movement > hw/mips/malta: Register the machine as a TypeInfo > hw/mips/malta: Introduce MaltaMachineClass::max_ramsize > hw/mips/malta: Introduce the 'malta-strict' machine > hw/mips/malta: Verify malta-strict machine uses correct DIMM sizes > > hw/mips/malta.c | 105 +++++++++++++++++++++++++++++++++++++++++------- > 1 file changed, 91 insertions(+), 14 deletions(-) > > -- > 2.21.3 > >