On 19.03.24 03:21, Chris Johns wrote:
Does this patch series build at the per commit level?
I used
./waf bspdefaults > a.txt
apply patch
./waf bspdefaults > b.txt
diff a.txt b.txt
to check that the defaults don't change. I will build the BSPs for each
commit today.
--
embedded brains GmbH
On 18.03.24 21:31, Kinsey Moore wrote:
Sorry, I didn't realize I had tests turned off in my local build when I
checked this. The test is now gated behind NEEDS_CLOCK_DRIVER as well.
This is fine for fixing the build, but I would rather fix the tests.
Applications may have there own clock drive
On 19.03.24 03:20, Chris Johns wrote:
On 19/3/2024 3:30 am, Sebastian Huber wrote:
---
spec/build/bsps/arm/xilinx-zynqmp-rpu/abi.yml| 2 +-
spec/build/bsps/arm/xilinx-zynqmp-rpu/bspmercuryxu5.yml | 2 +-
spec/build/bsps/arm/xilinx-zynqmp-rpu/linkcmds.yml | 2 +-
spec/buil
On 19.03.24 03:16, Chris Johns wrote:
On 19/3/2024 3:49 am, Sebastian Huber wrote:
Make the kernel I/O output character device flushing configurable. The
bsp_reset() function should reset the unit and do nothing else.
---
bsps/aarch64/xilinx-zynqmp/console/console.c | 3 ++-
bsps/aarch64/x
On 16/3/2024 1:14 am, Frank Kühndel wrote:
> Ping!
>
> The last discussion of this patch was
> https://lists.rtems.org/pipermail/devel/2024-February/077289.html
>
> Does the fact that I recive no further comments to this patch mean it can be
> pushed to the RTEMS User Manual as it is?
Sorry F
On 19/3/2024 1:27 am, Joel Sherrill wrote:
> I am going through the logs on the test sweep VMs to see why some builds are
> failing. This is due to gdb's requirement for GMP and MPFR. What's the
> recommended way to address this? Load native packages?
No, we need to add support to build them. We h
Does this patch series build at the per commit level?
Chris
On 19/3/2024 3:30 am, Sebastian Huber wrote:
> ---
> spec/build/bsps/dev/irq/optarmgic-icc-bpr0.yml| 6 +-
> spec/build/bsps/dev/irq/optarmgic-icc-igrpen0.yml | 6 +-
> spec/build/cpukit/optsmp.yml | 6 +
On 19/3/2024 3:30 am, Sebastian Huber wrote:
> ---
> spec/build/bsps/arm/xilinx-zynqmp-rpu/abi.yml| 2 +-
> spec/build/bsps/arm/xilinx-zynqmp-rpu/bspmercuryxu5.yml | 2 +-
> spec/build/bsps/arm/xilinx-zynqmp-rpu/linkcmds.yml | 2 +-
> spec/build/bsps/arm/xilinx-zynqmp-rpu/optpro
On 19/3/2024 3:49 am, Sebastian Huber wrote:
> Make the kernel I/O output character device flushing configurable. The
> bsp_reset() function should reset the unit and do nothing else.
> ---
> bsps/aarch64/xilinx-zynqmp/console/console.c | 3 ++-
> bsps/aarch64/xilinx-zynqmp/include/bsp.h |
No. Just a lesson to remember -- Everyone along the path should have built
rtems with all tests enabled.
This is something that should never happen after the upcoming transition to
GitLab. It definitely shows we need to build at least one BSP with tests
enabled.
On Mon, Mar 18, 2024, 7:45 PM zac
Do I need to do anything?
On Mon, 18 Mar 2024 at 16:38, Kinsey Moore wrote:
> Sorry, I didn't realize I had tests turned off in my local build when I
> checked this. The test is now gated behind NEEDS_CLOCK_DRIVER as well.
>
> Kinsey
>
> On Mon, Mar 18, 2024 at 4:15 AM Sebastian Huber <
> seba
Sorry, I didn't realize I had tests turned off in my local build when I
checked this. The test is now gated behind NEEDS_CLOCK_DRIVER as well.
Kinsey
On Mon, Mar 18, 2024 at 4:15 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> This patch breaks the build:
>
> In file included f
I think it would be wchar_t support in newlib.
On Mon, Mar 18, 2024 at 11:56 AM Joel Sherrill wrote:
>
> What does support for UTF-32 entail? Do you have an idea what software
> functions you are looking for?
>
> I see the International Components for Unicode (ICU) has a converter
> (https://ic
What does support for UTF-32 entail? Do you have an idea what software
functions you are looking for?
I see the International Components for Unicode (ICU) has a converter (
https://icu.unicode.org/download) which looks it might be part of a
solution.
Multibyte character methods defined by POSIX w
I want to add utf32 support.
Where do I start?
— John
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Make the kernel I/O output character device flushing configurable. The
bsp_reset() function should reset the unit and do nothing else.
---
bsps/aarch64/xilinx-zynqmp/console/console.c | 3 ++-
bsps/aarch64/xilinx-zynqmp/include/bsp.h | 2 --
.../console/console-config.c |
The use of this function is optional. Newer BSPs do not use it.
---
.../score/cpu/arm/armv4-isr-install-vector.c | 75 +++
cpukit/score/cpu/arm/cpu.c| 28 +--
spec/build/cpukit/cpuarm.yml | 1 +
3 files changed, 77 insertions(+), 27 deleti
Add a BSP variant without a board-specific name.
---
.../arm/xilinx-zynqmp-rpu/bspmercuryxu5.yml | 87 +--
.../bsps/arm/xilinx-zynqmp-rpu/bsprpu.yml | 17
spec/build/bsps/arm/xilinx-zynqmp-rpu/grp.yml | 69 +++
spec/build/bsps/arm/xilinx-zynqmp-rpu/obj.yml |
---
spec/build/bsps/dev/irq/optarmgic-icc-bpr0.yml| 6 +-
spec/build/bsps/dev/irq/optarmgic-icc-igrpen0.yml | 6 +-
spec/build/cpukit/optsmp.yml | 6 +-
3 files changed, 3 insertions(+), 15 deletions(-)
diff --git a/spec/build/bsps/dev/irq/optarmgic-icc-bpr0.y
---
spec/build/bsps/arm/xilinx-zynqmp-rpu/abi.yml| 2 +-
spec/build/bsps/arm/xilinx-zynqmp-rpu/bspmercuryxu5.yml | 2 +-
spec/build/bsps/arm/xilinx-zynqmp-rpu/linkcmds.yml | 2 +-
spec/build/bsps/arm/xilinx-zynqmp-rpu/optprocunitrpu.yml | 2 +-
4 files changed, 4 insertions(+),
Add a BSP variant without a board-specific name.
---
.../bsps/aarch64/xilinx-zynqmp/bspa53lp64.yml | 21 +++
.../bsps/aarch64/xilinx-zynqmp/optloadoff.yml | 1 +
.../bsps/aarch64/xilinx-zynqmp/optramori.yml | 1 +
spec/build/bsps/objxilinxsupportlp64.yml | 1 +
spec/build/
---
spec/build/bsps/objxilinxsupportr5.yml | 3 +--
spec/build/bsps/optxilsupportpath.yml | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/spec/build/bsps/objxilinxsupportr5.yml
b/spec/build/bsps/objxilinxsupportr5.yml
index d800b83247..25221c5e0d 100644
--- a/spec/build/bs
Hi
I am going through the logs on the test sweep VMs to see why some builds
are failing. This is due to gdb's requirement for GMP and MPFR. What's the
recommended way to address this? Load native packages?
checking for the correct version of gmp.h... yes
checking for the correct version of mpfr.h
This patch breaks the build:
In file included from ../../../cpukit/include/rtems/confdefs.h:64,
from
../../../testsuites/rhealstone/rhdeadlockbrk/deadlockbrk.c:215:
../../../cpukit/include/rtems/confdefs/clock.h:74:4: error: #error
"CONFIGURE_TICKS_PER_TIMESLICE shall be greate
24 matches
Mail list logo