Re: What to do with rtems_cache_disable_data()?

On 18/6/2024 12:02 am, Sebastian Huber wrote: > On 17.06.24 03:35, Chris Johns wrote: >> On 14/6/2024 10:42 pm, Peter Dufault wrote: >>> >>> >>>> On Jun 14, 2024, at 5:47 AM, Sebastian Huber >>>> wrote: >>>> >>>> Hello,

Re: What to do with rtems_cache_disable_data()?

On 14/6/2024 10:42 pm, Peter Dufault wrote: > > >> On Jun 14, 2024, at 5:47 AM, Sebastian Huber >> wrote: >> >> Hello, >> >> an user noticed that for example on the Xilinx Zynq 7000 BSP, the >> rtems_cache_disable_data() doesn't work. >> >> I had a look at this and managed to disable the L1 an

Re: Upgrading tools - gcc, binutils, and gdb

On 30/5/2024 7:22 am, Joel Sherrill wrote: > I am in the middle of updating gcc to the recent 13.3 release to move us off a > git hash. > > Is there any reason we are still on gdb 13? gdb 14.1 was released in Dec > 2023.  No reason. The change to 13 required python 3 but that has now been absorb

Re: ZynqMP APU RAM Start

On 14/5/2024 4:04 pm, Sebastian Huber wrote: > Hello, > > the ZynqMP APU RAM start addresses are far away from 0x0: > > cat spec/build/bsps/aarch64/xilinx-zynqmp/optramori.yml > SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause > actions: > - get-integer: null > - assert-uint32: null > - env-

Re: 6.1 release on Aug 26, 2024?

On 11/5/2024 9:40 pm, Cedric Berger wrote: > Hello, > > On gitlab, issues tagged "6.1" show a release date of Aug 26, 2024 for this > milestone, is it the current plan? > > If not, before or after? > > Any plan to merge GCC 13.3 or 14.1 before the release? > > Just curious, and trying to do som

RTOS/RTEMS (rtems.git) history rewrite

Hello, A merge request was applied that contained a merge commit and a decision was taken to correct this in the git repo. This means the history has been rewritten. Please check your forks or clones if you have updated and pulled in the merge commit. We are looking into getting GitLab to flag th

RTOS/RTEMS (rtems.git) history write

Hello, A merge request was applied that contained a merge commit and a decision was taken to correct this in the git repo. This means the history has been rewritten. Please check your forks or clones if you have updated and pulled in the merge commit. We are looking into getting GitLab to flag th

RTEMS Deployment

Hi, This email ask for the rtems-deployment repo to be moved RTEMS/Tools in GitLab. It is a repo of RSB configs to build packages of common or user specific vertical stacks. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mai

cgit

Hello, We will be shutting down cgit on git.rtems.org in coming days and the URL redirected to GitLab. If you have personal repos with things you would like to keep please make a local clone. Thanks Chris ___ devel mailing list devel@rtems.org http://l

Re: Cortex-M floating point (Was: RTEMS 6 branching)

On 2/5/2024 7:18 am, Cedric Berger wrote: > Hello, > > On 25.04.2024 02:16, Chris Johns wrote: >> I know I am getting ahead of myself but once we have GiLab running and you >> have >> a patch you would like merged please make a merge request. > > Done: > &

GitLab Workflows and Merge Requests

be buildable at each commit so a bisect of main does not break. If you need help please join the #gitlab-support channel on our Discord server. You can find our invite link here https://www.rtems.org/discord. We will also respond to posts on this list when we have the time. Regards Chris

Issues in GitLab

. We will also respond to posts on this list when we have the time. Regards Chris Johns RTEMS GitLab Team ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

RTEMS Project Repos in GitLab

imported from Trac. If you need help please join the #gitlab-support channel on our Discord server. You can find our invite link here https://www.rtems.org/discord. We will also respond to posts on this list when we have the time. Regards Chris Johns RTEMS GitLab Team

RTEMS GitLab Sign In

then please create an Administration issue detailing the roles you have If you need help please join the #gitlab-support channel on our Discord server. You can find our invite link here https://www.rtems.org/discord. We will also respond to posts on this list when we have the time. Regards

GitLab Launch

past months to help make this happen. If you need help please join the #gitlab-support channel on our Discord server. It is open to posts and questions. You can find our invite link here https://www.rtems.org/discord. We will also respond to posts on this list when we have the time. Regards Chris

Repo Transition to GitLab

Hi RTEMS Community The git repos on git.rtems.org are open and accepting patches. The GitLab repos will move us to main, something we have been waiting to do. Allowing commits into the repos means they will be brought across and played on top of the new main branch. We have changes in the repo on

Re: Cortex-M floating point (Was: RTEMS 6 branching)

On 24/4/2024 10:37 pm, Cedric Berger wrote: > Hello Sebastian, > > On 23.04.2024 19:56, Sebastian Huber wrote: >>> 1. Are all the things need for the release resolved? Tickets reviewed? >> It would be nice to have the interrupt get/set priority API in RTEMS 6. The >> Cortex-M floating point issue

Re: Cortex-M floating point (Was: RTEMS 6 branching)

On 24/4/2024 10:37 pm, Cedric Berger wrote: > Hello Sebastian, > > On 23.04.2024 19:56, Sebastian Huber wrote: >>> 1. Are all the things need for the release resolved? Tickets reviewed? >> It would be nice to have the interrupt get/set priority API in RTEMS 6. The >> Cortex-M floating point issue

Re: RTEMS 6 branching

On 25/4/2024 12:06 am, Peter Dufault wrote: >> On Apr 24, 2024, at 9:27 AM, Kinsey Moore wrote: >> >> That use case definitely wasn't considered for rtems-lwip and I don't know >> that it's ever been discussed. If that were intended, I'd expect a "./waf >> uninstall" target to exist that would r

RTEMS 6 branching

Hi, There has been some discussion about when we will branch and it is timely we discuss this. This is my input. :) While I create the releases I am not solely responsible for milestone dates or thresholds for a release. Please test the RC snaphots on our ftp server. Saying you have is as import

Re: [PATCH] bsps/powerpc: Introduction of interrupt locks

On 19/4/2024 6:12 pm, Christian MAUDERER wrote: > it is tested on an MVME2500 which uses the powerpc/qoriq_e500 in an SMP > configuration. Great and thanks. I should have access next week to MVME2700 hardware and can test it there. I doubt there will be an issue looking at the change but this grou

Re: RSB format changes to meet coding standard

On 19/4/2024 7:15 pm, andrew.butterfi...@scss.tcd.ie wrote: > Will you also do this with the formal code in rtems-central/formal ? Sorry, I do not use it so would prefer not to update it just yet. I think it best left to the leaders of that repo. > I do remember using yapf at some point – I have

RSB format changes to meet coding standard

Hi, I would like to run the python code we own through yapf and it's default to standardise the formatting and to being it inline with the coding standards. It would be good to do this before we branch for RTEMS 6. I can crate a patch and post if required but it will be noise and doubt anyone wil

Re: [RFC] rtems: Add options to kernel output char handler

On 18/4/2024 4:16 pm, Sebastian Huber wrote: > On 18.04.24 04:02, Chris Johns wrote: >> On 17/4/2024 11:06 pm, Sebastian Huber wrote: >>> Make the kernel I/O output character device processing configurable >>> through an option set parameter.  Add RTEMS_NO_OUTPUT and RT

Re: [PATCH] bsps/powerpc: Introduction of interrupt locks

Hi Vincenzo, Welcome to RTEMS. What hardware in the shared VME PowerPC family of BSPS has this change been tested on? Thanks Chris On 17/4/2024 5:34 pm, Vincenzo Calabretta wrote: > Interrupt locks are introduced in shared vme device drivers to enable > compilation in an SMP configuration of th

Re: [RFC] rtems: Add options to kernel output char handler

On 17/4/2024 11:06 pm, Sebastian Huber wrote: > Make the kernel I/O output character device processing configurable > through an option set parameter. Add RTEMS_NO_OUTPUT and RTEMS_FLUSH > options. The goal of this API change is to enable flushing the kernel > output device in the system terminat

Re: 6.1rc3 CentOS 7 Build Sweep Report

On 18/4/2024 4:13 am, Joel Sherrill wrote: > Hi > > 6.1rc3 appears to be in pretty good shape on CentOS 7 (w/GCC 8 and Python 3 > SCL). Results should be on the build@ list. One odd issue appears to be in the > rtems-tester. > > Testing a riscv-bsp with spike, I get this output. It is repeated wi

Re: Certificate of the documentation page expired yesterday

Thanks, it should be fixed. Chris On 13/4/2024 12:41 am, Heinz Junkes wrote: > Common Name (CN) > docs.rtems.org > Organisation (O) > > Organisational Unit (OU) > > Issued By > Common Name (CN) > R3 > Organisation (O) > Let's Encrypt > Organisational Unit (OU) > > Validity Period > Issued On >

Re: [PATCH v2 2/3] dev/serial: Add ZYNQ_UART_[01]_BASE_ADDR

On 4/4/2024 8:19 pm, Sebastian Huber wrote: > On 28.03.24 16:48, Kinsey Moore wrote: >> This patch set looks good to me. I'd suggest a different file for the versal >> unless there's a good name that can easily cover both. > > The versal BSP doesn't use this driver and seems to have a different

Re: [PATCH rtems-source-builder 1/2] glib: Update to 2.56.4

Looks good Chris On 6/3/2024 9:12 am, Kinsey Moore wrote: > This updates glib to 2.56.4 for AArch64 build support. > --- > bare/config/devel/glib-2.56.4-1.cfg| 30 ++ > bare/config/devel/qemu-couverture.bset | 2 +- > bare/config/devel/qemu-xilinx.bset | 2 +- >

Re: [RSB PATCH] sb: Add sb-rtems-pkg to update the RTEMS package hashes and checksums

On 4/4/2024 6:54 am, Kinsey Moore wrote: > On Wed, Apr 3, 2024 at 2:11 PM Chris Johns <mailto:chr...@rtems.org>> wrote: > >> On 4 Apr 2024, at 3:52 am, Kinsey Moore > <mailto:kinsey.mo...@oarcorp.com>> wrote: >> Looks fine overall. Minor nits: &

Re: [RSB PATCH] sb: Add sb-rtems-pkg to update the RTEMS package hashes and checksums

> On 4 Apr 2024, at 3:52 am, Kinsey Moore wrote: > > Looks fine overall. Minor nits: > "host" is set to "freebsd" and is never used. The tool uses simhost so it could be any host listed in that module and it references that table. Nothing is built but needed to creat a build object. Simhost i

Re: [Bugfix rtems-lwip 1/4] Fix definition of portTICK_RATE_MS

On 1/4/2024 9:49 am, Bernd Moessner wrote: > The FreeRTOS define portTICK_RATE_MS must represent the time in ms > between two system ticks. > --- > rtemslwip/xilinx/xlwipopts.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/rtemslwip/xilinx/xlwipopts.h b/rtemslwip/xilinx

RTEMS Trac Ticket to GitLab import

Hi RTEMS Community GitLab transition is progressing better than we expected and we are now at a point where we want to move the tickets in Trac to GitLab. A lot of preparation has been done in planning the move and an outcome we had not planned is the time it will take is much more. The original p

Re: Xilinx header files installed by BSP

On 27/3/2024 7:14 am, Kinsey Moore wrote: > On Mon, Mar 25, 2024 at 3:34 PM Bernd Moessner > wrote: > > > On 25.03.2024 13:26, Sebastian Huber wrote: > > Hello, > > > > the BSPs for the Xilinx Zynq/ZynqMP/Versal platforms use code from > > Xi

Re: [PATCH v2 2/3] dev/serial: Add ZYNQ_UART_[01]_BASE_ADDR

On 28/3/2024 6:43 am, Sebastian Huber wrote: > This helps to provide a shared implementation of the kernel I/O support. > --- > bsps/aarch64/xilinx-zynqmp/console/console.c | 4 +- > bsps/aarch64/xilinx-zynqmp/include/bsp.h | 2 + > bsps/arm/xilinx-zynq/console/console-config.c | 5 +- >

Re: [PATCH v2] bsps: Add BSP_FLUSH_KERNEL_CHAR_OUTPUT BSP option

On 21/3/2024 5:39 pm, Sebastian Huber wrote:> On 21.03.24 00:28, Chris Johns wrote: >> On 21/3/2024 2:11 am, Sebastian Huber wrote: >>> On 19.03.24 18:44, Chris Johns wrote: >>>> On 20/3/2024 2:03 am, Sebastian Huber wrote: >>>>> On 19.03.24 14:50, Kin

Re: [PATCH v2] bsps: Add BSP_FLUSH_KERNEL_CHAR_OUTPUT BSP option

On 21/3/2024 2:11 am, Sebastian Huber wrote: > On 19.03.24 18:44, Chris Johns wrote: >> On 20/3/2024 2:03 am, Sebastian Huber wrote: >>> On 19.03.24 14:50, Kinsey Moore wrote: >>>> The xilinx-zynqmp-rpu bsp_reset() is modified, but not included in the spec >>&g

Re: [PATCH v2] bsps: Add BSP_FLUSH_KERNEL_CHAR_OUTPUT BSP option

On 19/3/2024 7:39 pm, 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. This changes existing behaviour. RTEMS is poor at cleanly handling the console output on reset. Working with the

Re: [PATCH v2] bsps: Add BSP_FLUSH_KERNEL_CHAR_OUTPUT BSP option

On 20/3/2024 2:03 am, Sebastian Huber wrote: > On 19.03.24 14:50, Kinsey Moore wrote: >> The xilinx-zynqmp-rpu bsp_reset() is modified, but not included in the spec >> file for the new option. Its family differs from the arm/xilinx-zynqmp BSP >> family with a -rpu suffix. > > Yes, but this BSP is

Re: [PATCH 1/5] bsps: Use bsps/aarch64/xilinx-zynqmp

On 19/3/2024 5:59 pm, Sebastian Huber wrote: > 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 ch

Re: [PATCH 3/5] xilinx-zynqmp-rpu: Remove URLs from copyrights

On 19/3/2024 5:52 pm, Sebastian Huber wrote: > 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/bspmer

Re: [PATCH v2] user: Add docu for use of Rust with RTEMS

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

Re: RTEMS 7 GDB Build Failure on FreeBSD 13

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

Re: [PATCH 1/5] bsps: Use bsps/aarch64/xilinx-zynqmp

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 +

Re: [PATCH 3/5] xilinx-zynqmp-rpu: Remove URLs from copyrights

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

Re: [PATCH] bsps: Add BSP_FLUSH_KERNEL_CHAR_OUTPUT option

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 |

Re: rtems-6.1-rc2 on Mac OSX Sonoma 14.4 (Apple M2) failed -> fixed

On 12/3/2024 8:06 pm, Heinz Junkes wrote: > Hello Chris, > > thanks for your mail. I have now installed the python as you described. Great. > The source-builder process runs quite well. > > Unfortunately, the gcc-13.2.0-newlib for powerpc cannot be built: I updated to the latest RSB with the

RTEMS GitLab

Hi RTEMS Community I would like to announce that RTEMS will be moving to GitLib in the coming month or so. We do not have any exact dates yet and we will let you know when we do. The change is large and complex because we are integrating an active open source project made up of various pieces into

Re: [PATCH rtems-source-builder 1/2] rtems-tools-6.cfg: Bump hash to account for 5 months of changes

OK Thanks Chris On 14/3/2024 7:00 am, Joel Sherrill wrote: > In particular, the BSP set definitions for rtems-bsp-builder were > out of sync with RTEMS and caused unnecessary failures reported to > the build@ mailing list. > --- > rtems/config/tools/rtems-tools-6.cfg | 4 ++-- > 1 file changed,

Re: [PATCH rtems-tools] rtems-score-thread.ini: Remove _Thread_Close so trace examples link

OK Thanks Chris On 12/3/2024 1:06 am, Joel Sherrill wrote: > _Thread_Close no longer exists. There are multiple exapmles which > show tracing in rtems-examples which fail to link due to this. > --- > linkers/rtems-score-thread.ini | 5 ++--- > 1 file changed, 2 insertions(+), 3 deletions(-) > >

Re: rtems-6.1-rc2 on Mac OSX Sonoma 14.4 (Apple M2) failed -> fixed

[ Sorry, my email does not show your message ] Hi Heinz, I see you are using brew on your M machine which is fine. As an alternative I have documented using python.org: https://docs.rtems.org/branches/master/user/hosts/macos.html#python and a virtual environment. Chris On 12/3/2024 2:09 pm,

Re: Multiple PowerPC BSPs Fail to BUIld

On 11/3/2024 6:04 pm, Sebastian Huber wrote: > sorry for breaking the build. I fixed it. The problem is that > header file depends on the BSP-provided define BSP_SHARED_HANDLER_SUPPORT. So, > the include order matters. Thank you for quickly sorting this out. Chris ___

Re: [PATCH 4/6] build: Add support to make bootloader images

On 7/3/2024 5:27 pm, Sebastian Huber wrote: > On 07.03.24 02:09, Chris Johns wrote: >> On 6/3/2024 8:33 am, Gedare Bloom wrote: >>> If script generation needs to be done, it should be implemented in >>> Python with input from the yml spec item as necessary to fill out

Re: Multiple PowerPC BSPs Fail to BUIld

On 10/3/2024 8:40 am, Joel Sherrill wrote: > Hi > > In looking at the build sweep log, I see what looks like motorola_powerpc and > beatnik all have a common build failure that results in 53 configurations > failing per > > https://lists.rtems.org/pipermail/build/2024-March/051698.html > > This

Re: [PATCH 4/6] build: Add support to make bootloader images

On 6/3/2024 8:33 am, Gedare Bloom wrote: > If script generation needs to be done, it should be implemented in > Python with input from the yml spec item as necessary to fill out a > templated script with variables to customize for the BSP, and with > appropriate injection of comments etc to allow t

Re: [PATCH 5/6] build: Add mkimage support for powerpc/qoriq

On 4/3/2024 6:35 pm, Sebastian Huber wrote: > On 04.03.24 08:22, Chris Johns wrote: >>> diff --git a/spec/build/bsps/powerpc/qoriq/mkimage.yml >>> b/spec/build/bsps/powerpc/qoriq/mkimage.yml >>> new file mode 100644 >>> index 00..712fd237b1 >

Re: [PATCH 5/6] build: Add mkimage support for powerpc/qoriq

On 28/2/2024 2:15 am, Sebastian Huber wrote: > Update #4272. > --- > spec/build/bsps/optpython.yml | 14 > spec/build/bsps/optubootmkimage.yml | 20 > spec/build/bsps/powerpc/qoriq/grp.yml | 6 > spec/build/bsps/powerpc/qoriq/mkimage.yml | 39 +

Re: [PATCH 4/6] build: Add support to make bootloader images

On 1/3/2024 9:57 pm, Sebastian Huber wrote: > On 29.02.24 00:05, Chris Johns wrote: >>>> If it is will the details be exported in the pkgconfig file and made >>>> available >>>> for users building applications in a consistent and easy to use way? >>&

Re: [RFC] libdl: Make Elf_Sym::st_other available

On 1/3/2024 6:05 pm, Sebastian Huber wrote: > On 29.02.24 00:27, Chris Johns wrote: >> On 27/2/2024 6:46 pm, Sebastian Huber wrote: >>> The 64-bit PowerPC ELFv2 relocation support needs access to the >>> Elf_Sym::st_other symbol information.  The machine-specific relo

Re: [PATCH] build: Use -frandom-seed=0

On 29/2/2024 6:36 pm, Sebastian Huber wrote: > On 29.02.24 00:29, Chris Johns wrote: >> On 28/2/2024 6:24 pm, Sebastian Huber wrote: >>> On 28.02.24 06:34, Chris Johns wrote: >>>> The manual says: >>>> >>>>     The string can either be a n

Re: 6.1rc2 on Rocky 9

On 1/3/2024 2:43 am, Joel Sherrill wrote: > Hi > > Looks pretty good overall. This appears to be the only issue: > > Testing: riscv rv64imac_spike > BSP to Build: rv64imac > 'distclean' finished successfully (0.011s) > Regenerate build specification cache (needs a couple of seconds)... > > real

Re: [RTEMS Tools 1/4] linkers: Avoid void pointer arithmetic

OK too all and thanks Chris On 26/2/2024 8:41 pm, Sebastian Huber wrote: > --- > linkers/rtems-syms.cpp | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/linkers/rtems-syms.cpp b/linkers/rtems-syms.cpp > index f0ac2bb..9fe552e 100644 > --- a/linkers/rtems-syms.cpp >

Re: [PATCH] build: Use -frandom-seed=0

On 28/2/2024 6:24 pm, Sebastian Huber wrote: > On 28.02.24 06:34, Chris Johns wrote: >> The manual says: >> >>    The string can either be a number (decimal, octal or hex) or >>    an arbitrary string (in which case it’s converted to a number by >>    computing C

Re: [RFC] libdl: Make Elf_Sym::st_other available

On 27/2/2024 6:46 pm, Sebastian Huber wrote: > The 64-bit PowerPC ELFv2 relocation support needs access to the > Elf_Sym::st_other symbol information. The machine-specific relocation handler > had only access to the Elf_Sym::st_info symbol information. This change > extends the 8-bit syminfo para

Re: [Tools] add libiberty/argv.c for mingw32 build

OK Thanks Chris On 28/2/2024 7:25 pm, Sebastian Huber wrote: > From: zhengxiaojun > > Signed-off-by: zhengxiaojun > > Close #4974. > --- > rtemstoolkit/wscript | 10 -- > 1 file changed, 4 insertions(+), 6 deletions(-) > > diff --git a/rtemstoolkit/wscript b/rtemstoolkit/wscript > i

Re: [PATCH 4/6] build: Add support to make bootloader images

On 28/2/2024 6:44 pm, Sebastian Huber wrote: > On 28.02.24 06:48, Chris Johns wrote: >> Hi, >> >> Is this to allow BSP ready output to be created from the build system? > > Yes, this is the goal. Nice and thanks for looking into this. >> If it is will the det

Re: [Tools] rtemstoolkit/libierty: Add missing file

OK and thanks Chris On 27/2/2024 9:56 pm, Sebastian Huber wrote: > This fixes the following build error for --host=x86_64-w64-mingw32: > > rtemstoolkit/libiberty.a(pex-win32.c.18.o): in function `win32_spawn': > rtemstoolkit/libiberty/pex-win32.c:643: undefined reference to `writeargv' > > Upda

Re: [Tools] rtemstoolkit/libierty: Add missing file

OK and thanks Chris On 27/2/2024 9:56 pm, Sebastian Huber wrote: > This fixes the following build error for --host=x86_64-w64-mingw32: > > rtemstoolkit/libiberty.a(pex-win32.c.18.o): in function `win32_spawn': > rtemstoolkit/libiberty/pex-win32.c:643: undefined reference to `writeargv' > > Upda

Re: [PATCH 4/6] build: Add support to make bootloader images

Hi, Is this to allow BSP ready output to be created from the build system? If it is will the details be exported in the pkgconfig file and made available for users building applications in a consistent and easy to use way? Is this output created along side the ELF file? Does this approach handl

Re: [PATCH 1/6] build: Fix script action

On 28/2/2024 2:15 am, Sebastian Huber wrote: > We have to use a custom dictorary to be able to set the "value" argument Spelling. :) Chris > in the exec() context. > > Update #4272. > --- > wscript | 10 -- > 1 file changed, 8 insertions(+), 2 deletions(-) > > diff --git a/wscript b/w

Re: [PATCH] build: Use -frandom-seed=0

Hi, The manual says: The string can either be a number (decimal, octal or hex) or an arbitrary string (in which case it’s converted to a number by computing CRC32). The string should be different for every file you compile. I take this to mean the option `-frandom-seed=0` uses `0` as a

Re: [PATCH] powerpc: Use RTEMS_XCONCAT()

OK Thanks Chris On 28/2/2024 2:20 am, Sebastian Huber wrote: > Prefer macros with a proper namespace. > --- > cpukit/score/cpu/powerpc/include/rtems/asm.h | 10 -- > 1 file changed, 4 insertions(+), 6 deletions(-) > > diff --git a/cpukit/score/cpu/powerpc/include/rtems/asm.h > b/cpukit

Re: 6.1rc2 Tool Build Failures

On 24/2/2024 7:04 am, Joel Sherrill wrote: => rtems 6.1rc2 has a lot of tool build failures because I didn't have gmp-devel > installed. > > hecking for gmp.h... no > configure: error: gmp.h header not found > > This is reported as part of building gcc-newlib. Should the RSB account for > this >

Documentation theme update

Hi, I have a patch for rtems-docs.git to move us to the pip installed sphinx-rtd-theme removing the custom theme based on sphinx-rtd-theme we currently use. The ticket is #4994. The patch is over 4M in size as it deletes common/sphinx_rtd_theme_rtems. YOu can download it from: https://ftp.rte

Documentation theme update

Hi, I have a patch for rtems-docs.git to move us to the pip installed sphinx-rtd-theme removing the custom theme based on sphinx-rtd-theme we currently use. The ticket is #4994. The patch is over 4M in size as it deletes common/sphinx_rtd_theme_rtems. YOu can download it from: https://ftp.rte

Re: Incorrect Rendering in Rate Monotonic Manager Chapter

On 10/2/2024 8:06 am, Joel Sherrill wrote: > Hi > > https://docs.rtems.org/branches/master/c-user/rate-monotonic/background.html#schedulability-analysis > > > has a bullet list which does not

Re: [PATCH rtems-docs 1/1] user: Add docu for use of Rust with RTEMS

mbH & Co. KG > +| |copy| 2016, 2024 embedded brains GmbH & Co. KG > | |copy| 2016, 2019 Sebastian Huber > | |copy| 2012, 2022 Chris Johns > | |copy| 2012, 2020 Gedare Bloom > @@ -51,5 +51,6 @@ RTEMS User Manual (|version|). > > tools/index

Re: [PATCH] wscript: Update install directory to include RTEMS Version

Hi, Looks good with the addition of a loop shown befow. Did you install into a clean path and test the BSP list can be reported in rtems-test? Chris On 20/2/2024 2:27 pm, aaron.nyh...@unfoldedeffective.com wrote: > From: Aaron N > > Closes #4929 > --- > config/wscript | 2 +- > linke

Re: [PATCH] testsuites/dl11: Test TLS on a secondary thread

Looks good. Thanks Chris On 19/2/2024 3:16 pm, Kinsey Moore wrote: > This adds a pthread that runs the test as well to increase test > coverage. The original test would have passed if all threads returned > the address of the Init task's errno since no additional threads or > tasks were checked.

Re: [PATCH] improved error checking in ticks per timeslice

On 18/2/2024 4:42 am, Gedare Bloom wrote: > Is there a simple way we can add some checks for modification of > generated files into a commit hook? And then, point to a documentation > that helps explain where to go for more guidance depending on the code > generation source? We are moving to GitLa

RSB checksum updates for RTEMS 6

Hi, I have opened https://devel.rtems.org/ticket/4991 to track checksum errors in some of the sources being downloaded by the RSB such as: error: checksum failure file: patches/Make-lang.in-b09fb02bb4c0d16fc2c842bec4069c033897b5f2.patch I am seeing this error while I attempt to create 6.1-rc2. I

Re: [PATCH v2 0/5] libtest: Add packet processor

On 13/2/2024 7:33 pm, Sebastian Huber wrote: > independent of the packet processor patch, can I check in the base64 and CRC > patches? Yes and thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH v2 5/5] libtest: Add packet processor

On 13/2/2024 7:32 pm, Sebastian Huber wrote: > Hello Chris, > > sorry for the delay. > > On 07.02.24 00:56, Chris Johns wrote: >> On 5/2/2024 9:13 pm, Sebastian Huber wrote: >>> Hello Chris, >>> >>> thanks for having a look at it. >&

Re: [PATCH rtems-source-builder 1/2] Update libtool to 2.4.7 for AArch64 support

OK Thanks Chris On 12/2/2024 1:51 pm, Kinsey Moore wrote: > --- > bare/config/devel/autotools-base.bset | 2 +- > bare/config/devel/libtool-2.4.7-1.cfg | 17 + > bare/config/devel/libtool.bset| 2 +- > 3 files changed, 19 insertions(+), 2 deletions(-) > create mode 100

Re: Question regarding ARMV7M FPU context switch and ISRs

Sorry as I sent this I could see the subject and 7M. Chris On 9/2/2024 1:33 pm, Chris Johns wrote: > On 8/2/2024 9:55 pm, Sebastian Huber wrote: >> On 08.02.24 11:43, Cedric Berger wrote: >>> On 08.02.2024 11:09, Sebastian Huber wrote: >>>> On 08.02

Re: Question regarding ARMV7M FPU context switch and ISRs

On 8/2/2024 9:55 pm, Sebastian Huber wrote: > On 08.02.24 11:43, Cedric Berger wrote: >> On 08.02.2024 11:09, Sebastian Huber wrote: >>> On 08.02.24 10:53, Cedric Berger wrote: This would also simplify the context switching code, by centralizing of the saving of the FPU context in RT

Re: [PATCH v2 5/5] libtest: Add packet processor

On 5/2/2024 9:13 pm, Sebastian Huber wrote: > Hello Chris, > > thanks for having a look at it. > > On 02.02.24 00:14, Chris Johns wrote: >> Hi, >> >> Thanks for the updated documentation, protocol and use cases. It has helped. >> Now >> I underst

Re: [PATCH v2 5/5] libtest: Add packet processor

Hi, Thanks for the updated documentation, protocol and use cases. It has helped. Now I understand some of the context I have raised further questions about it I feel we should resolve. Without a protocol version number being exchanged it limits how we can grow and develop this protocol beyond wher

Re: [PATCH rtems-source-builder 2/2] qemu: Update CFLAGS and LDFLAGS overrides

OK to push Chris On 31/1/2024 8:37 am, Kinsey Moore wrote: > QEMU used to honor LDFLAGS and CFLAGS and has since moved to accepting > them via --extra-cflags and --extra-ldflags options to configure. > --- > source-builder/config/qemu-common-2.cfg | 4 ++-- > 1 file changed, 2 insertions(+), 2 d

Re: [PATCH rtems-source-builder 1/2] source-builder: Handle modern pkg-config symlinks

On 31/1/2024 8:36 am, Kinsey Moore wrote: > Modern versions of pkg-config include new architecture-specific symlinks > that are sometimes checked before "pkg-config". Oh that is a shame they have done this. Seems messy to me. > This causes builds to > detect the system pkg-config instead of the

Re: [PATCH rtems-source-builder] bare/config/qemu-5.2.0: Add gdbus-codegen patch

OK Thanks Chris On 1/2/2024 6:30 am, Kinsey Moore wrote: > --- > bare/config/devel/qemu-5.2.0-1.cfg | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/bare/config/devel/qemu-5.2.0-1.cfg > b/bare/config/devel/qemu-5.2.0-1.cfg > index 3c8186b..ac476ad 100644 > --- a/bare/config/deve

Re: [RTEMS Tools 0/1] trace/wscript: Improve C++ standard selection

On 25/1/2024 12:33 am, Sebastian Huber wrote: > - Am 24. Jan 2024 um 0:55 schrieb Chris Johns chr...@rtems.org: > >> On 23/1/2024 5:55 pm, Sebastian Huber wrote: >>> - Am 22. Jan 2024 um 22:56 schrieb Chris Johns chr...@rtems.org: > [...] >>> The usa

Re: [PATCH rtems6 1/1] libmisc/shell: Fix timeout in getting terminal size

On 23/1/2024 9:00 pm, Peter Dufault wrote: >> On Jan 22, 2024, at 1:51 PM, Peter Dufault wrote: >>> On Jan 22, 2024, at 12:16 PM, Gedare Bloom wrote: >>> >>> I have a couple minor notes below. More important, does this change >>> require updating documentation? >> >> I'd have to look to see if th

Re: [RTEMS Tools 0/1] trace/wscript: Improve C++ standard selection

On 23/1/2024 5:55 pm, Sebastian Huber wrote: > - Am 22. Jan 2024 um 22:56 schrieb Chris Johns chr...@rtems.org: > >> On 22/1/2024 6:18 pm, Sebastian Huber wrote: >>> On 22.01.24 00:47, Chris Johns wrote: >>>> On 22/1/2024 3:42 am, Sebastian Huber wrote: >&g

Re: [RTEMS Tools 0/1] trace/wscript: Improve C++ standard selection

On 22/1/2024 6:18 pm, Sebastian Huber wrote: > On 22.01.24 00:47, Chris Johns wrote: >> On 22/1/2024 3:42 am, Sebastian Huber wrote: >>> Does XCode ship a Symbolize.h and llvm-config? >> >> No ... >> >> % uname -a >> Darwin weka.contemporary.net

Re: Convert test executables to bootloader images?

On 23/1/2024 5:27 am, Sebastian Huber wrote: > - Am 22. Jan 2024 um 0:22 schrieb Chris Johns chr...@rtems.org: > >> On 17/1/2024 11:39 pm, Sebastian Huber wrote: >>> Hello, >>> >>> attached is a proof of concept. Using a ./waf bootimages command didn&

Re: [PATCH 3/4] dev/io: Add a CRC-24Q implementation

On 23/1/2024 8:01 am, Gedare Bloom wrote: > On Mon, Jan 22, 2024 at 11:13 AM Sebastian Huber > wrote: >> >> Hello Gedare, >> >> - Am 22. Jan 2024 um 17:49 schrieb Gedare Bloom ged...@rtems.org: >> >>> Similar to the other patch, this looks mostly useful. >>> >>> I think a lot of these kind of

Re: [RTEMS Tools 0/1] trace/wscript: Improve C++ standard selection

On 22/1/2024 3:42 am, Sebastian Huber wrote: > Does XCode ship a Symbolize.h and llvm-config? No ... % uname -a Darwin weka.contemporary.net.au 23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020 arm64 % c++ -v Apple clang version 15.0.0 (c

Re: [PATCH 0/4] dev/io: Add packet processor

Hi, There are a few things I do not understand about this addition. I brief review of the code seems OK but I am struggling to understand the requirements driving this addition. Can a ticket please be created with the requirements and a real world use case of how it would be used and what problem(

  1   2   3   4   5   6   7   8   9   10   >