These two options are really useful to avoid needless typing in QEMU by
making files and environment variables available to barebox from outside.
Document them outside of the pytest --help text as well.
Signed-off-by: Ahmad Fatoum
---
Documentation/boards/emulated.rst | 12
1 file
Labgrid v25.0 allows this to be empty, so let's drop it where unneeded.
Signed-off-by: Ahmad Fatoum
---
test/arm/a15@multi_v7_defconfig.yaml | 1 -
test/arm/a9@multi_v7_defconfig.yaml | 1 -
test/arm/qemu-raspi0@multi_v5_v6_defconfig.yaml | 1 -
test/arm/qemu-raspi1a
The --env and --fs options are very useful for passing stuff into QEMU
without having to assemble images or type stuff into the console.
Document them and add a new --graphic option that spawns either a Bochs
ISA, PCI or a ramfb graphic device depending on the target.
Ahmad Fatoum (4):
test: up
This new option will take care to provide a suitable graphics device.
How it's displayed can be customized via --qemu -display $OUTPUT.
For this to work, we must instruct labgrid not to set -nographic or
-display itself, which is possible via setting qemu-default since
Labgrid v25.0.
Signed-off-b
This gives us better error messages when QEMU startup fails, allows us
to drop the extra_args key and allows suppressing Labgrid
-display/-nographic option fixups.
Signed-off-by: Ahmad Fatoum
---
Documentation/boards/emulated.rst | 6 ++
test/Containerfile| 2 +-
test/strateg
Hello,
I could enable CONFIG_DEBUG_LL in the 1st stage, but not
CONFIG_DEBUG_PBL because I got an error:
"input image too big. Maximum is 61436 bytes, got x bytes" where
x > 61436. The on-chip RAM is 64KB.
When I enable CONFIG_DEBUG_LL in the 1st stage, I get the following
output, wh
ARM: mmu64: fix flag confusion during early_remap_range
early_remap_range takes a generic map type parameter like MAP_UNCACHED
or ARCH_MAP_CACHED_RWX, while get_pte_attrs returns the actual bitmask
that should go into the page table entry.
Signed-off-by: Ahmad Fatoum
---
arch/arm/cpu/mmu_64.c |
