[PATCH 2/2] testsuites/dhrystone: Initialize before use

This resovles a warning where a variable could be used before it is initialized in some code paths. --- testsuites/benchmarks/dhrystone/dhry_1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testsuites/benchmarks/dhrystone/dhry_1.c b/testsuites/benchmarks/dhrystone/dhry_1.c

Re: [PATCH 0/2] GSOC: ​Hello World exercise

Thanks for taking this step toward participating in GSoC! I took a look at the images in the binary patch and they look good. If you need to send more images in the future, please use a link instead of sharing them in a binary patch. Kinsey On Wed, Feb 28, 2024 at 2:33 AM Ning Yang wrote: >

[PATCH rtems-libbsd] freebsd/mmcsd: Disable on-device cache usage

This disables any usage of the on-device R/W cache since all device cache maintenance functions are compiled out under RTEMS leaving no way to flush the cache before system reset and making data loss possible. --- freebsd/sys/dev/mmc/mmcsd.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 0/2] GSOC: ​Hello World exercise

Hello, My name is Yang Ning, a computer science master's student at China Yanshan University.My research chiefly focuses on RTEMS. This is my first contact with operating system-related projects. I have been study RTEMS on RPi4 for half year. During the half year,I configured and builded RTEMS

[PATCH 1/2] hello world exercise

--- hello/hello.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hello/hello.c b/hello/hello.c index d2321d8..e074563 100644 --- a/hello/hello.c +++ b/hello/hello.c @@ -8,6 +8,6 @@ rtems_task Init( rtems_task_argument ignored) { - puts("hello, world!"); +

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

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 index 20b1047..0611e2e 100644 --- a/rtemstoolkit/wscript +++ b/rtemstoolkit/wscript

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

On 28.02.24 08:20, zhengxiaojun wrote: The patch close #4974. Sorry, I didn't notice this ticket. I will rebase your patch to the current master since the build system part is an improvement. -- embedded brains GmbH & Co. KG Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email:

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

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. 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: [PATCH 0/6] Add support for optional BSP-specific tools to make bootloader images

On 27.02.24 21:39, Gedare Bloom wrote: I'm a little confused by this patch set. I think I saw Frank makes a similar kind of comment. Basically, I don't understand why we generate these tools with the RTEMS build system, inside of rtems.git, rather than inside of rtems-tools. The BSP build

Re: [PATCH 3/6] build: Make OBJCOPY optional

On 28.02.24 06:36, Chris Johns wrote: Why do we need this? The tool objcopy is always built when the tools are built? I am not sure if objcopy is provided by clang and under which name. -- embedded brains GmbH & Co. KG Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email:

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

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 CRC32). The string should be different for every file you compile. I take this to mean the

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

The patch close #4974. On 2024/2/28 15:11, Chris Johns wrote: 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':

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' > >

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' > >

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

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

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 >

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

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

joel said: +#if CONFIGURE_TICKS_PER_TIMESLICE <= 0 && > defined(CONFIGURE_TICKS_PER_TIMESLICE) > + #error "CONFIGURE_TICKS_PER_TIMESLICE shall be greater than zero" > +#endif > + > > > This is modifying the right file but I think it is safer to check that > it is defined >

Re: [RFC] generic CAN/CAN FD susbsytem for RTEMS from scratch (LinCAN inspired)

On Mon, Feb 12, 2024 at 8:03 AM Pavel Pisa wrote: > > Dear RTEMS community, the core developers team, > > Michal Lenc works on a new generic CAN/CAN FD subsystem for RTEMS under my > supervision. The project has reached a phase where we will be very grateful > for the review and pointing to

Re: [PATCH 0/6] Add support for optional BSP-specific tools to make bootloader images

I'm a little confused by this patch set. I think I saw Frank makes a similar kind of comment. Basically, I don't understand why we generate these tools with the RTEMS build system, inside of rtems.git, rather than inside of rtems-tools. On Tue, Feb 27, 2024 at 8:15 AM Sebastian Huber wrote: > >

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

Hello Sebastian, On 2/27/24 16:15, Sebastian Huber wrote: Add a new build item type to provide optional BSP-specific tools to make bootloader images. The tools are installed as Python scripts in: ${prefix}/bin/rtems-mkimage-${ARCH}-${BSP_NAME}.py Application build systems can query the

[PATCH] powerpc: Use RTEMS_XCONCAT()

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/score/cpu/powerpc/include/rtems/asm.h index 27af64e724..94f54245b4 100644

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

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 +++ 4 files changed, 79 insertions(+)

[PATCH 3/6] build: Make OBJCOPY optional

Update #4272. --- spec/build/bsps/i386/pc386/objsmpstart.yml | 4 +++- spec/build/bsps/optobjcopy.yml | 14 +- 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/spec/build/bsps/i386/pc386/objsmpstart.yml b/spec/build/bsps/i386/pc386/objsmpstart.yml index

[PATCH 1/6] build: Fix script action

We have to use a custom dictorary to be able to set the "value" argument in the exec() context. Update #4272. --- wscript | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/wscript b/wscript index a71e0d3f10..6c81083b2c 100755 --- a/wscript +++ b/wscript @@ -1026,8

[PATCH 0/6] Add support for optional BSP-specific tools to make bootloader images

Sebastian Huber (6): build: Fix script action build: Add "find-optional-program" action build: Make OBJCOPY optional build: Add support to make bootloader images build: Add mkimage support for powerpc/qoriq build: Add mkimage support for arm/xilinx-zynq

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

Add a new build item type to provide optional BSP-specific tools to make bootloader images. The tools are installed as Python scripts in: ${prefix}/bin/rtems-mkimage-${ARCH}-${BSP_NAME}.py Application build systems can query the tool using the RTEMS_MKIMAGE package configuration varible, for

[PATCH 2/6] build: Add "find-optional-program" action

Update #4272. --- wscript | 12 1 file changed, 12 insertions(+) diff --git a/wscript b/wscript index 6c81083b2c..e43ae8ba3e 100755 --- a/wscript +++ b/wscript @@ -976,6 +976,17 @@ class OptionItem(Item): def _find_program(self, conf, cic, value, arg): return

[PATCH 6/6] build: Add mkimage support for arm/xilinx-zynq

Update #4272. --- spec/build/bsps/arm/xilinx-zynq/grp.yml | 6 spec/build/bsps/arm/xilinx-zynq/mkimage.yml | 39 + 2 files changed, 45 insertions(+) create mode 100644 spec/build/bsps/arm/xilinx-zynq/mkimage.yml diff --git a/spec/build/bsps/arm/xilinx-zynq/grp.yml

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

This makes the build reproducible. --- spec/build/bsps/opto0.yml | 1 + spec/build/bsps/opto1.yml | 1 + spec/build/bsps/opto2.yml | 1 + spec/build/bsps/optog.yml | 1 + spec/build/bsps/optos.yml | 1 + 5 files changed, 5 insertions(+) diff --git a/spec/build/bsps/opto0.yml

[Tools] rtemstoolkit/libierty: Add missing file

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' Update #4969. --- rtemstoolkit/libiberty/argv.c | 568

[RFC] libdl: Make Elf_Sym::st_other available

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 parameter to 16-bit and uses the additional 8-bits to

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

On 19.02.24 03:13, zakthertems...@gmail.com wrote: +#if defined(CONFIGURE_TICKS_PER_TIMESLICE) + #if CONFIGURE_TICKS_PER_TIMESLICE <= 0 +#error "CONFIGURE_TICKS_PER_TIMESLICE shall be greater than zero" + #endif +#endif This should be #if defined(CONFIGURE_TICKS_PER_TIMESLICE) &&

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

ping On Tue, 20 Feb 2024 at 20:25, zack leung wrote: > ping > > On Sun, 18 Feb 2024 at 21:15, wrote: > >> --- >> cpukit/doxygen/appl-config.h | 2 +- >> cpukit/include/rtems/confdefs/clock.h | 6 ++ >> 2 files changed, 7 insertions(+), 1 deletion(-) >> >> diff --git

Patch with modified hello world

SeifalrahmanAhmedAlfakharany.patch Description: Binary data ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel

[RTEMS Tools 4/4] rld: Recognize 64-bit PowerPC

Close #4995. --- rtemstoolkit/rld-elf.cpp | 1 + 1 file changed, 1 insertion(+) diff --git a/rtemstoolkit/rld-elf.cpp b/rtemstoolkit/rld-elf.cpp index 8b55818..b131461 100644 --- a/rtemstoolkit/rld-elf.cpp +++ b/rtemstoolkit/rld-elf.cpp @@ -1178,6 +1178,7 @@ namespace rld { "m68k",

[RTEMS Tools 2/4] linkers: Constify read-only data

--- linkers/rtems-syms.cpp | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/linkers/rtems-syms.cpp b/linkers/rtems-syms.cpp index 9fe552e..377007d 100644 --- a/linkers/rtems-syms.cpp +++ b/linkers/rtems-syms.cpp @@ -53,7 +53,7 @@ /** * Header text. */

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

--- 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 +++ b/linkers/rtems-syms.cpp @@ -322,9 +322,9 @@ output_sym::operator ()(const

[RTEMS Tools 3/4] linkers: Allow generation of symbol map file only

If a symbol map file is specified by the user and no output file, then just generate the symbol map file. The user can then compile the file using its own build jobs. --- linkers/rtems-syms.cpp | 22 -- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git

6.1rc2 Tool Build Failures

Hi 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 by building gmp at the same time? For now, I installed a

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

From: Frank Kühndel --- user/index.rst | 3 +- user/overview/index.rst | 2 + user/rust/bare-metal.rst | 548 +++ user/rust/index.rst | 64 + 4 files changed, 616 insertions(+), 1 deletion(-) create mode 100644

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

Hi Chris, thanks for reviewing this patch. On 2/21/24 03:42, Chris Johns wrote: Hi Frank Thanks for this, it ia awesome. On 17/2/2024 7:52 am, Frank Kuehndel wrote: From: Frank Kühndel --- user/index.rst | 3 +- user/overview/index.rst | 2 + user/rust/bare-metal.rst |

Re: Documentation theme update

Based on Christian saying it works and me confirming that, I pushed this. Thanks a lot Chris! --joel On Wed, Feb 21, 2024 at 2:22 AM Christian MAUDERER < christian.maude...@embedded-brains.de> wrote: > Hello Chris, > > On 2024-02-21 06:16, Chris Johns wrote: > > Hi, > > > > I have a patch for

[PATCH] bsps/xnandpsu: Allow creation of BBT

This fixes a logic inversion that was preventing creation of a Bad Block Table (BBT) from scratch on devices that lack one. This was discovered during upstream integration testing. The BBT management layer in this driver is not designed to be easily testable other than on real hardware. ---

Re: Documentation theme update

Hello Chris, On 2024-02-21 06:16, Chris Johns wrote: 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. I think reducing RTEMS specific adaptions is a great idea. So thank you for

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:

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:

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

Hi Frank Thanks for this, it ia awesome. On 17/2/2024 7:52 am, Frank Kuehndel wrote: > From: Frank Kühndel > > --- > user/index.rst | 3 +- > user/overview/index.rst | 2 + > user/rust/bare-metal.rst | 549 +++ > user/rust/index.rst |

GSoC24 and Mentors

Hey folks, RTEMS was accepted as an org for GSoC again. If you were a mentor in the previous two years, and would like to be a mentor again, simply go activate your 2024 mentor account at g.co/gsoc If you were not a mentor in the past, but would like to be, please send me/Joel/Chris an email and

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 +- >

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

ping On Sun, 18 Feb 2024 at 21:15, wrote: > --- > cpukit/doxygen/appl-config.h | 2 +- > cpukit/include/rtems/confdefs/clock.h | 6 ++ > 2 files changed, 7 insertions(+), 1 deletion(-) > > diff --git a/cpukit/doxygen/appl-config.h b/cpukit/doxygen/appl-config.h > index

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

On Sun, Feb 18, 2024 at 3:31 PM Chris Johns wrote: > > 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

[PATCH v2 2/2] testsuites/jffs2: Add test for empty NOR FS

This adds a test to very that remounting a completely used, but empty NOR JFFS2 filesystem is possible. Previously, this triggered an edge condition in the JFFS2 scan code that prevented remount of a correctly formed and uncorrupted filesystem. --- .../testsuites/fstests/fsjffs2empty01.yml |

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

From: Aaron N Closes #4929 --- config/wscript | 2 +- linkers/wscript| 2 +- misc/tools/boot.py | 2 +- misc/wscript | 4 ++-- rtemstoolkit/macros.py | 3 +++ rtemstoolkit/wscript | 4 ++-- tester/covoar/wscript | 4 ++-- tester/rt/options.py | 2 +-

[PATCH v2 1/2] cpukit/jffs2: Handle used empty file system

On JFFS2 file systems on NOR flash or dataflash that does not have spare area for metadata and thus does not invoke delayed writes, it is possible to put the file system into a state where all blocks have been written to and all files have been deleted from the filesystem. There is a bug in the

QEMU IRL not modeled

Debugging some qemu interrupts with the uarts on the microblaze platform. I noticed i was getting some transactions failed on the qemu side. interrupt at pc=802dec88 msr=1a2 0 iflags=100 Transaction failed: vaddr 0x41200024 physaddr 0x41200024 size 4 access type DATA_LOAD Transaction

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

I think this is ok also. On Sun, Feb 18, 2024, 10:20 PM Chris Johns wrote: > 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 >

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.

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

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. --- testsuites/libtests/dl11/dl-load.c | 72 +++---

[PATCH] improved error checking in ticks per timeslice

--- cpukit/doxygen/appl-config.h | 2 +- cpukit/include/rtems/confdefs/clock.h | 6 ++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/cpukit/doxygen/appl-config.h b/cpukit/doxygen/appl-config.h index bd7cde628f..d480eb3971 100644 --- a/cpukit/doxygen/appl-config.h +++

[PATCH rtems-docs] user/zynqmp-rpu: Update boot suggestion

Change the development suggestion for booting the R5 since the R5 u-boot is only minimally functional without significant development. This also adds caveats when booting the R5 cores from the A53. --- user/bsps/arm/xilinx-zynqmp-rpu.rst | 14 -- 1 file changed, 12 insertions(+), 2

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

[PATCH] improved error checking in ticks per timeslice

From: Zack leung diff --git a/cpukit/doxygen/appl-config.h b/cpukit/doxygen/appl-config.h index bd7cde628f..d480eb3971 100644 --- a/cpukit/doxygen/appl-config.h +++ b/cpukit/doxygen/appl-config.h @@ -3312,7 +3312,7 @@ * @parblock * The following constraints apply to this configuration

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

On Sat, Feb 17, 2024 at 10:35 AM Sebastian Huber wrote: > > On 17.02.24 18:11, Joel Sherrill wrote: > > > > On Wed, Feb 14, 2024, 9:54 PM zack leung > > wrote: > > > > > This file is generated from something in rtems-central. This was at > > the > > >

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

On 17.02.24 18:11, Joel Sherrill wrote: On Wed, Feb 14, 2024, 9:54 PM zack leung > wrote: > This file is generated from something in rtems-central. This was at the > top of the file: > >   * This file is part of the RTEMS quality process and

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

On Wed, Feb 14, 2024, 9:54 PM zack leung wrote: > > This file is generated from something in rtems-central. This was at the > > top of the file: > > > > * This file is part of the RTEMS quality process and was automatically > > * generated. If you find something that needs to be fixed or >

Re: [PATCH rtems-source-builder 2/2] devel/qemu-xilinx: Fix build on GCC 13.2.0

On Wed, Feb 14, 2024 at 1:37 PM Kinsey Moore wrote: > On Wed, Feb 14, 2024 at 9:14 AM Sam Price wrote: > >> I was wondering if you had any notes on your process of working with >> qemu in the rtems builder. >> I imagine you have your own xilinx qemu forked to work on, and then >> take the

[PATCH] spec/zynqmp-rpu: Clean up options

The RAM origin had an unnecessary alignment requirement and the RAM lenght had a reference that couldn't possibly be used. This removes those obsolete option specifiers. --- spec/build/bsps/arm/xilinx-zynqmp-rpu/optramlen.yml | 2 -- spec/build/bsps/arm/xilinx-zynqmp-rpu/optramori.yml | 1 - 2

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

From: Frank Kühndel --- user/index.rst | 3 +- user/overview/index.rst | 2 + user/rust/bare-metal.rst | 549 +++ user/rust/index.rst | 64 + 4 files changed, 617 insertions(+), 1 deletion(-) create mode 100644

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

From: Frank Kühndel This is the long promised Rust on RTEMS step-by-step guide. For reviewing it, I suggest the natural order: 1) user/rust/index.rst -- The introduction 2) user/rust/bare-metal.rst -- The step-by-step guide If you prefer reviewing the PDF or HTML, you can download them

Re: RSB checksum updates for RTEMS 6

On Fri, Feb 16, 2024, 12:56 AM Chris Johns wrote: > 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: >

Re: RSB checksum updates for RTEMS 6

On 16.02.24 07:55, Chris Johns wrote: I have openedhttps://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

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.

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. >>> >>> On 02.02.24 00:14, Chris Johns wrote: Hi,

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

> This file is generated from something in rtems-central. This was at the > top of the file: > > * This file is part of the RTEMS quality process and was automatically > * generated. If you find something that needs to be fixed or > * worded better please post a report or patch to an RTEMS

Re: [PATCH rtems-source-builder 2/2] devel/qemu-xilinx: Fix build on GCC 13.2.0

I was trying to debug while only some of the uart interrupt vectors seem to work on the microblaze. I thought it would be nice to compile qemu with debug flags. Also eventually I would like to develop my own firmware driver emulation for qemu. Which would probably require me to have my own qemu

Re: [PATCH rtems-source-builder 2/2] devel/qemu-xilinx: Fix build on GCC 13.2.0

On Wed, Feb 14, 2024 at 9:14 AM Sam Price wrote: > I was wondering if you had any notes on your process of working with > qemu in the rtems builder. > I imagine you have your own xilinx qemu forked to work on, and then > take the patches and integrate them into the rsb builder? > Nothing so

Re: [PATCH rtems-source-builder 2/2] devel/qemu-xilinx: Fix build on GCC 13.2.0

I was wondering if you had any notes on your process of working with qemu in the rtems builder. I imagine you have your own xilinx qemu forked to work on, and then take the patches and integrate them into the rsb builder? Thanks, Sam On Sun, Feb 11, 2024 at 9:51 PM Kinsey Moore wrote: > > GCC

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

On 14.02.24 15:18, Joel Sherrill wrote: I'm cc'ing Sebastian because you edited the text in a generated file. He should be able to point us to the right place to fix it. On Mon, Feb 12, 2024 at 8:26 PM > wrote: From: Zack leung

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

I'm cc'ing Sebastian because you edited the text in a generated file. He should be able to point us to the right place to fix it. On Mon, Feb 12, 2024 at 8:26 PM wrote: > From: Zack leung > > diff --git a/cpukit/doxygen/appl-config.h b/cpukit/doxygen/appl-config.h > index

Apparently Unused ARM Linker Symbol

Hi In looking at linkcmds code, one of the folks in the class noticed this symbol which appears to be unused. This is a grep from the top of the tree. It appears that bsp_stack_main_size is defined but never really used. If someone can confirm this, it needs to be purged. [joel@localhost rtems]$

Wrong BSP Names in arm spec files

Hi While teaching a class this week, I noticed that some arm optcachedata.yml files appear to reference BSP variants that are not associated with the BSP whose directory the yml file is located in. These greps show the issue: [joel@localhost arm]$ grep lm3s6965_qemu */optcachedat*

Re: [PATCH] i386: Restore SMP functionality

On 12.02.24 15:34, Kinsey Moore wrote: When the switch to waf occurred, the SMP support in i386 was left out causing it to accumulate a minor amount of cruft. This enables SMP for the i386 BSPs that support it and updates them for the API drift that has occurred since the change. Looks good.

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

Hello, independent of the packet processor patch, can I check in the base64 and CRC patches? -- embedded brains GmbH & Co. KG Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email: sebastian.hu...@embedded-brains.de phone: +49-89-18 94 741 - 16 fax: +49-89-18 94 741 - 08

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

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. On 02.02.24 00:14, Chris Johns wrote: Hi, Thanks for the updated documentation, protocol and use cases. It has helped. Now I

[PATCH] improved error checking in ticks per timeslice

From: Zack leung diff --git a/cpukit/doxygen/appl-config.h b/cpukit/doxygen/appl-config.h index bd7cde628f..d480eb3971 100644 --- a/cpukit/doxygen/appl-config.h +++ b/cpukit/doxygen/appl-config.h @@ -3312,7 +3312,7 @@ * @parblock * The following constraints apply to this configuration

[PATCH] improved error checking in ticks per timeslice

From: Zack leung diff --git a/cpukit/doxygen/appl-config.h b/cpukit/doxygen/appl-config.h index bd7cde628f..d480eb3971 100644 --- a/cpukit/doxygen/appl-config.h +++ b/cpukit/doxygen/appl-config.h @@ -3312,7 +3312,7 @@ * @parblock * The following constraints apply to this configuration

[PATCH] bsps/qspipsu: Calculate correct parallel mode size

Stacked mode doubles the number of sectors and device size while parallel mode doubles the sector size and the device size. Make sure that this is accounted for in the device size accessor. --- bsps/shared/dev/spi/xqspipsu-flash-helper.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

[RFC] generic CAN/CAN FD susbsytem for RTEMS from scratch (LinCAN inspired)

Dear RTEMS community, the core developers team, Michal Lenc works on a new generic CAN/CAN FD subsystem for RTEMS under my supervision. The project has reached a phase where we will be very grateful for the review and pointing to required changes to start a discussion of possible inclusion

[PATCH] i386: Restore SMP functionality

When the switch to waf occurred, the SMP support in i386 was left out causing it to accumulate a minor amount of cruft. This enables SMP for the i386 BSPs that support it and updates them for the API drift that has occurred since the change. --- cpukit/score/cpu/i386/cpu_asm.S | 2

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

[PATCH rtems-source-builder 2/2] devel/qemu-xilinx: Fix build on GCC 13.2.0

GCC 13.2.0 adds new warnings/errors when mixing ints and enums. This changes the pminsn helper type to correctly use enums. --- bare/config/devel/qemu-xilinx-v2020.2-1.cfg | 7 +++ 1 file changed, 7 insertions(+) diff --git a/bare/config/devel/qemu-xilinx-v2020.2-1.cfg

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

--- 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 100644 bare/config/devel/libtool-2.4.7-1.cfg diff --git

Incorrect Rendering in Rate Monotonic Manager Chapter

Hi https://docs.rtems.org/branches/master/c-user/rate-monotonic/background.html#schedulability-analysis has a bullet list which does not have bullets. But they are there in the PDF version: https://docs.rtems.org/branches/master/c-user.pdf Is there something wrong with the markup? Is something

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.24 10:53, Cedric Berger wrote: > >

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

<    1   2   3   4   5   6   7   8   9   10   >