there or we may use multi:name format for those that cannot have a
main architecture. Or we can list them with multiple names, one for each
arch so any of them could be used and on start to select the machine and
the binary can check that all of the listed archs are compiled in.
Specifying the a
ap`` is now an alias for ``raspi,model=3A+``
+- `raspi3b`` is now an alias for ``raspi,model=3B``
+- `raspi4b`` is now an alias for ``raspi,model=4B``
This is not how we typically handle "we have a bunch
of different devboards in one family". What's wrong with the
existing
writes:
On Sat, 1 Feb 2025 at 12:57, BALATON Zoltan wrote:
On Sat, 1 Feb 2025, Philippe Mathieu-Daudé wrote:
- Deprecate the 'raspi4b' machine name, renaming it as
'raspi4b-1g' on 32-bit hosts, 'raspi4b-2g' otherwise.
- Add the 'raspi4b-4g' and 'rasp
th
-memory so that could also select the revision as a convenience if this
is tied to a specific revision.
Regards,
BALATON Zoltan
Philippe Mathieu-Daudé (7):
hw/arm/raspi4b: Declare machine types using DEFINE_TYPES() macro
hw/arm/raspi4b: Introduce abstract raspi4-base machine type
hw/arm
