Re: [PATCH 00/47] Add TMS570LC4357 support

2024-01-15 Thread Sebastian Huber
Hello Pavel, I checked in the patch set with an update commit message for [PATCH 24/47] bsp/tms570: Remove double pin configuration and an updated README patch. I still have to review the chip errata for the TMS570LC4357. This will likely result in some changes in the system initialization se

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

2024-01-15 Thread Sebastian Huber
The I/O packet processor provides a simple mechanism to exchange reliable and in-order data through transmitting and receiving one character at a time. The I/O packet processor does not buffer data. The processor uses a stop-and-wait automatic repeat request method. There is at most one packet in

[PATCH 1/4] dev/io: Make base64 encoding tables public

2024-01-15 Thread Sebastian Huber
This makes them reusable. Change the character type to uint8_t. --- cpukit/dev/iobase64.c | 24 +--- cpukit/include/rtems/dev/io.h | 10 ++ 2 files changed, 27 insertions(+), 7 deletions(-) diff --git a/cpukit/dev/iobase64.c b/cpukit/dev/iobase64.c index 0ac70

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

2024-01-15 Thread Sebastian Huber
The I/O packet processor provides a simple mechanism to exchange reliable and in-order data through transmitting and receiving one character at a time. The I/O packet processor does not buffer data. The processor uses a stop-and-wait automatic repeat request method. There is at most one packet in

[PATCH 2/4] dev/io: Add base64 decoder

2024-01-15 Thread Sebastian Huber
From: Matthew Joyce --- cpukit/dev/iobase64decode.c | 166 cpukit/include/rtems/dev/io.h | 63 ++ spec/build/cpukit/librtemscpu.yml | 1 + .../build/testsuites/unit/unit-no-clock-0.yml | 1 + testsuites/unit/tc-io-base64-dec

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

2024-01-15 Thread Sebastian Huber
--- cpukit/dev/iocrc24q.c | 148 ++ cpukit/include/rtems/dev/io.h | 41 + spec/build/cpukit/librtemscpu.yml | 1 + .../build/testsuites/unit/unit-no-clock-0.yml | 2 + testsuites/unit/tc-io-packet.c| 42 +

Fwd: [RTEMS Project] #60: GNATS: Additional state

2024-01-15 Thread Joel Sherrill
Looks like one of the commits has the wrong ticket number. And this ticket should be closed anyway. We haven't used GNATS in a long time. -- Forwarded message - From: RTEMS trac Date: Mon, Jan 15, 2024, 3:37 AM Subject: Re: [RTEMS Project] #60: GNATS: Additional state To: Cc:

Fwd: [RTEMS Project] #45: shsim does not build

2024-01-15 Thread Joel Sherrill
And this is the other half of the ticket number. -- Forwarded message - From: RTEMS trac Date: Mon, Jan 15, 2024, 3:37 AM Subject: Re: [RTEMS Project] #45: shsim does not build To: Cc: #45: shsim does not build ---+- Reporter

[RTEMS Tools] linkers: Use push/pop section

2024-01-15 Thread Sebastian Huber
Restore the previous section, otherwise the generated code may end up in a wrong section. --- linkers/rtems-syms.cpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/linkers/rtems-syms.cpp b/linkers/rtems-syms.cpp index 699c014..ecdcd15 100644 --- a/linkers/rtems-syms.cpp +++

Re: Fwd: [RTEMS Project] #60: GNATS: Additional state

2024-01-15 Thread Sebastian Huber
On 15.01.24 17:38, Joel Sherrill wrote: Looks like one of the commits has the wrong ticket number. It seems everything which matches with #[0-9]+ is associated with a ticket, here it was the subject: bsp/tms570: TMS570LC4x Errata DEVICE#60 -- embedded brains GmbH & Co. KG Herr Sebastian HUB