Axel Heider

extra boot info pages should not be executable

3

Currently the boot info frame is mapped non-executable, but the extra boot info pages are mapped executable. There seems no good use case why the extra boot info should be...

define device memory explicitly

3

Currently device untypeds are created for all physical memory from 0 to `CONFIG_PADDR_USER_DEVICE_TOP` that is not marked as reserved. This approach simplifies platform specific address space management from the kernel's...

Test Hypervisor support with Cortex-A72

5

We are about to add RasPi4 support, which has a Cortex-A72. It still needs to be tested that seL4 Hypervisor support with Cortex-A72 works as expected, that is why we...

Generic check that the timer does not run backwards or rolls over

10

This is a follow-up from the discussion at https://github.com/seL4/seL4/pull/646 that the system timer must never roll over or run backwards. It seems there is no sanity check in the kernel...

Use physical addresses in the boot flow until caps are created

4

It seems the boot flow can be simplified if memory management is done based on physical addresses. That also makes porting easier, as this is the natural platform view, having...

Unify boot flow of ARM and RISC-V

1

The boot flow on ARM and RISC-V are largely similar, thus is seems worth to unify them. Either the common parts are factored out in a shared file, so the...

Provide a way to control kernel output verbosity, especially during the boot process. While details are helpful for porting or building new systems, they tend to get annoyingly verbose when...

provide example how to match against a string list

13

Signed-off-by: Axel Heider ### Why: Show how list of string can be used. This is for both convenience and avoiding redundancy. ### What's being changed: Provide an example

Typing the caret char ("^") does not print anything

4

Typing the caret char ("^") does not print anything on Geany 1.36/Linux

Please create a release package for the 0.13.2 release at https://github.com/riscv/riscv-debug-spec/releases, the versions that are currently shown there just just release process experiments https://riscv.org/technical/specifications/ points to the floating https://github.com/riscv/riscv-debug-spec/blob/release/riscv-debug-release.pdf, this...