Hello,
This patch removed the previous git build of qemu and qem4 replacing it
with 5.2.0-rc1. I can build on FreeBSD and run the network tests for the
Xilinx Zynq BSP.
QEMU 5.2.0 has moved to the meson build system so you will need to make
sure you have Ninja install as meson layers on top of Ni
From: Chris Johns
- This version of qemu uses meson and ninja to build. You will need
to install ninja to build. No checks are made until meson run
---
.../{qemu4-git-1.cfg => qemu-5.2.0-1.cfg} | 18 +--
bare/config/devel/qemu.bset | 2 +-
bare/config/devel/qemu4.bset
Hello,
This patch removed the previous git build of qemu and qem4 replacing it
with 5.2.0-rc1. I can build on FreeBSD and run the network tests for the
Xilinx Zynq BSP.
QEMU 5.2.0 has moved to the meson build system so you will need to make
sure you have Ninja install as meson layers on top of Ni
From: Chris Johns
- This version of qemu uses meson and ninja to build. You will need
to install ninja to build. No checks are made until meson run
---
.../{qemu4-git-1.cfg => qemu-5.2.0-1.cfg} | 16 +-
bare/config/devel/qemu.bset | 2 +-
bare/config/devel/qemu4.bset
On 12/11/20 6:50 pm, Sebastian Huber wrote:
> On 12/11/2020 08:30, Chris Johns wrote:
>
>> I am not sure. For example ...
>>
>> https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging
>>
>> ... has a picture of the wire links needed to enable debugging. We need to be
>> able to qu
---
freebsd/sys/arm64/arm64/in_cksum.c| 243 +++
freebsd/sys/arm64/include/machine/armreg.h| 665 ++
freebsd/sys/arm64/include/machine/cpu.h | 203 ++
freebsd/sys/arm64/include/machine/cpufunc.h | 153
freebsd/sys/arm64/include/machine/in_cksum.
The SUBALIGN(4) required on rtemsroset and rtemsrwset for ILP32 builds
was previously present on LP64 builds and causes no issues within RTEMS,
but causes relocation/alignment issues when building libbsd. This
restricts those alignment changes to ILP32 builds.
---
bsps/aarch64/shared/start/linkcmd
These files are required for libbsd to build against the AArch64 A53
BSPs.
---
spec/build/bsps/aarch64/grp.yml | 4
1 file changed, 4 insertions(+)
diff --git a/spec/build/bsps/aarch64/grp.yml b/spec/build/bsps/aarch64/grp.yml
index 4b5f998a12..e0a8e607a5 100644
--- a/spec/build/bsps/aarch64
This name better reflects the execution envirnoment in which the cache
is fully loaded with valid data unrelated to the body request handler.
Update #3199.
---
eng/test-framework.rst | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/eng/test-framework.rst b/eng/t
Report all runtime measurement environments with a name only and encode
the worker count of the "Load" environment in the name.
Update #3199.
---
eng/test-framework.rst | 21 +++--
1 file changed, 7 insertions(+), 14 deletions(-)
diff --git a/eng/test-framework.rst b/eng/test-fra
Hello,
I checked in the first round of the generated RTEMS API headers and the
corresponding documentation. This includes the Event Manager, IO
Manager, and the Partition Manager:
https://docs.rtems.org/branches/master/c-user/event/directives.html
https://docs.rtems.org/branches/master/c-use
11 matches
Mail list logo