| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change reworks how the meta-xilinx layer enables and provides the
custom version of QEMU based on Xilinx's fork of QEMU. The existing
implementation relied on the single sysroot which was changed in oe-core
such that now recipes have their own sysroots (RSS support).
Additionally oe-core now provides the QEMU binaries to the runqemu
script via the 'qemu-helper-native' recipes sysroot as opposed to the
image sysroot.
These rework changes allow for a single machine to select the targeted
QEMU version as well as to provide the qemuboot config specific to the
targeted QEMU version. The selection of QEMU version is now handled by
PREFERRED_PROVIDER mechanics with the meta-xilinx layer providing an
additional recipe that is equivalent to qemu-helper-native and which
also provides said target allowing for the machine to select via the use
of PREFERRED_PROVIDER_qemu-helper-native. This recipe
(qemu-xilinx-helper-native) however instead provides the sysroot
populated with qemu-xilinx instead of qemu.
Additionally the XILINX_QEMUBOOT variable is replaced with the
qemuboot-xilinx.bbclass, this provides the overrides for setting up
qemu-xilinx specific QB_* args. Additionally this bbclass points runqemu
at the qemu-xilinx-helper-native sysroot for QEMU binaries.
These changes also work towards making the meta-xilinx layer better
handle multiple qemuboot.conf variants as well as handling different
QEMU versions.
This change also removes the 'qemu-system-xilinx' MACHINE_FEATURES, this
is due to MACHINE_FEATURES no longer being available for native recipes.
Additionally there is no longer any logic that needs to know this any
way.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Reviewed-by: Alistair Francis <alistair.francis@xilinx.com>
|
| |
|
|
|
|
|
|
| |
Avoid using the MACHINE_DEVICETREE variable for detection of the device
tree that needs to be loaded. Instead only rely on IMAGE_BOOT_FILES or
KERNEL_DEVICETREE.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the use of MACHINE_DEVICETREE for providing sources to
device-tree, instead provide the device tree sources as SRC_URI entires.
Whilst this was already being done automatically by the
MACHINE_DEVICETREE logic it also created a non-standard way of providing
the device tree sources to the recipe.
The setup of SRC_URI is done via the use of a device-tree.bbappend
instead of directly in the device-tree.bb recipe itself. This is for two
reason, separation of the source from the build logic as well as to
provide an example for how a user can extend the device-tree recipe to
provide custom device tree sources in their layer.
This change also moves the paths to the sources around, this is to align
the names of the directories to match the OVERRIDES so that when
expanding the file paths it will search the subdirs based on the
OVERRIDES or machine names.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Move the setup of network devices to the new QB_NETWORK_DEVICE variable,
this avoids the need to configure slirp or tap options from the machine
configuration.
Additionally this provides the benefit of letting runqemu handle the
setup of tap and slirp arguments, allowing for it to provide features
such as host-guest port forwarding for slirp.
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Tested-by: Alistair Francis <alistair.francis@xilinx.com>
|
|
|
Rename the QEMU machines to match the <board>-<design>-<arch>
convention. QEMU only machines no longer need to be named qemu*.
Note for qemuzynq it is special in that it does not model a board, as
such it has no board in the name being just 'qemu-zynq7'.
This updates the README.md to match the new machine names.
Additional update all occurrences of the qemu* machines
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Reviewed-by: Alistair Francis <alistair.francis@xilinx.com>
|
