![[RTEMS Logo]](/images/logo.png){kind=logo}
Timeline
03/16/23:
- 02:34 RTEMSMailingLists edited by Chris Johns
- Make is clear to use an email (diff)
03/14/23:
- 22:44 Ticket #4879 (Use Cortex-Mx fault registers to show more information about the fault ...) created by kgardas
- It would be great if _CPU_Exception_frame_print would use a little bit …
- 06:43 Ticket #4878 (sptests/spsysinit01 sem_open call only has 3 parameters with O_CREAT ...) closed by Sebastian Huber <sebastian.huber@…>
- fixed: In [changeset:"377eae4165d52d247bdeaac99c735fdb02edae65/rtems" 377eae4/rtems]: […]
03/13/23:
- 14:29 Ticket #4878 (sptests/spsysinit01 sem_open call only has 3 parameters with O_CREAT ...) created by Lucian-Raul Silistru
- Cloned from #4877: ---- When calling sem_open with the O_CREAT flag …
- 14:28 Ticket #4877 (sptests/spsysinit01 sem_open call only has 3 parameters with O_CREAT flag) reopened by Sebastian Huber
- Thanks, you found the reason for a sporadic test failure which is on my TODO list for a long time.
- 13:31 Ticket #4877 (sptests/spsysinit01 sem_open call only has 3 parameters with O_CREAT flag) closed by Joel Sherrill
- invalid: This is an error on the caller's part. Per https://pubs.opengroup.org/onlinepubs/9699919799/functions/sem_open.html, the fourth argument is required if you include O_CREAT. Since you did not explicitly pass a value, the result is undefined. […]
- 09:26 Ticket #4877 (sptests/spsysinit01 sem_open call only has 3 parameters with O_CREAT flag) created by Lucian-Raul Silistru
- When calling sem_open with the O_CREAT flag the sem_open function …
03/11/23:
- 15:20 GSoC/2023 edited by Mohd Noor Aman
- Entry for GSoC 2023 by Mohd Noor Aman (diff)
03/09/23:
- 23:38 Ticket #4872 (GDB 13.1 does not build on FreeBSD 13.1) closed by Chris Johns <chrisj@…>
- fixed: In [changeset:"e5abdec8534849c9362674e867154121e917aead/rtems-source-builder" e5abdec/rtems-source-builder]: […]
- 14:21 Ticket #4876 (RISC-V BSP Variant for the Kendryte K210 SoC) created by Alan Cudmore
- The Kendryte K210 is low cost 64-bit dual core RISC-V SoC with: - …
- 12:54 Ticket #4874 (Undefined behaviour) closed by Sebastian Huber
-
wontfix: This was discussed on the RTEMS mailing list some time ago:
https://lists.rtems.org/pipermail/devel/2021-November/069991.html
Quite frankly, someone passing a NULL pointer to functions like
void rtems_clock_get_monotonic_bintime(struct bintime *time_point)will also use the NULL pointer later. The next release of the pre-qualified RTEMS will probably contain theclock_get()function which performs these NULL pointer checks. - 12:42 Ticket #4875 (LEON3FT - Power-down workaround) created by Daniel Páscoa
- Within bsps\sparc\leon3\start\bspidle.S there is the attached code …
- 12:37 Ticket #4874 (Undefined behaviour) created by Daniel Páscoa
- If one searches within SRSs or ICDs for 'undefined behaviour' one will …
- 12:34 Ticket #4873 (Registers definitions wrongly defined when there are reserved bits) closed by Daniel Páscoa
- duplicate: Wrong ticket raised.
- 12:32 Ticket #4873 (Registers definitions wrongly defined when there are reserved bits) created by Daniel Páscoa
- With respect to RTEMS 6 (ESA-promoted RTEMS SMP Qualification Data …
- 07:35 GSoC/Mentors edited by Husni Faiz
- (diff)
- 03:10 Ticket #4872 (GDB 13.1 does not build on FreeBSD 13.1) created by Chris Johns
- If the binutils package is installed GDB does not build. See …
03/06/23:
- 03:40 Ticket #4768 (Use tarballs for stable versions development tools) reopened by Chris Johns
-
I am reopening this ticket. The severity is blocker and if a release is not to used upstream released tarball files we need a clear reason why.
The RSB is not using GCC released sources and the current rtems/config/tools/rtems-gcc-10-newlib-head.cfg shows this.
If you look at the 5.3 sources you will see gcc tarballs are used, eg
gcc-9.3.0.tar.xz. As things are an RTEMS 6 release will end up with a file calledgnu-mirror-gcc-92b44cf,tar.gz. Where is the repo this comes from? The namegnu-mirror-gccis confusing unless you understand what is going on? How do you track the integrity of the repo used once you manage to find it? I think we should be using a GCC release tarball of code in releases. - 02:35 Ticket #4870 (Add features for QSPI Flash on Xilinx Versal) created by Aaron N
- Adds bug fixes for code ported from Xilinx, adds ReadId? function for …
- 02:27 Ticket #4869 (Add QSPI Flash Device API) created by Aaron N
- Add an API for qspi flash to create device node.
03/03/23:
- 15:48 Ticket #4868 (Add a note about email signup to Mailman page.) created by Amar Takhar
- We need to add a note to the mailman page to allow for users to signup …
- 14:35 Ticket #4867 (Clean up rtems-lwip uLan directory) created by Kinsey Moore
- The uLan directory in rtems-lwip was originally sourced from another …
Note: See TracTimeline
for information about the timeline view.
