![[RTEMS Logo]](/images/logo.png){kind=logo}
Timeline
03/08/23:
- 20:39 Changeset in rtems-docs [fd6d8620] by Kinsey Moore <kinsey.moore@…>
- c-user/chains: Correct iteration example code Casting the node returned by rtems_chain_head is incorrect. That node is owned by the control structure and use of it post-cast could cause memory corruption. Instead, use rtems_chain_first which returns the node after the head node. This also corrects node->next to rtems_chain_next(node) which makes better use of the API.
- 19:01 Changeset in rtems [10ff982] by Kinsey Moore <kinsey.moore@…>
- bsps/xnandpsu: Allow use of both chip selects By default, the Xilinx NAND driver does not probe the second chip select. This alteration allows the second half of chips to be detected when present.
- 15:32 Changeset in rtems-source-builder [7153c2f] by Alex White <alex.white@…>
- 6: Update MicroBlaze? gdb to 12.1 GDB 11.2 fails to compile on Ubuntu 22.04 for MicroBlaze?.
03/06/23:
- 15:37 Changeset in rtems [3612dc7] by Sebastian Huber <sebastian.huber@…>
- build: Print item UID in case of errors This helps to identify issues in build items.
- 10:44 Changeset in rtems-central [2fe6710] by Sebastian Huber <sebastian.huber@…>
- spec: Add missing interface function link
- 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 …
03/02/23:
- 22:56 Changeset in rtems-lwip [8dfd35f] by Kinsey Moore <kinsey.moore@…>
- rtemslwip: Use interrupt server for ISRs lwIP requires locking to be available in its device ISRs. This is incompatible with RTEMS ISRs, but could be worked around on single-core systems. This moves lwIP device ISR execution to a task via the interrupt server. All network device driver code should use the interrupt server going forward.
- 22:30 Changeset in rtems-lwip [64d9819] by Kinsey Moore <kinsey.moore@…>
- lwip/api: Notify about dropped packets The receive UDP and raw mailboxes will silently drop packets once the mailbox is full. This provides a debug message if debugging is enabled when this is the case to direct the user toward a solution.
03/01/23:
02/28/23:
- 04:49 Changeset in rtems [fe6a5d0] by Maldonado, Sergio E. (GSFC-580.0) <sergio.e.maldonado@…>
- bsps/microblaze: Fix UART transmit interrupt
- 04:44 Changeset in rtems [c627a132] by Maldonado, Sergio E. (GSFC-580.0) <sergio.e.maldonado@…>
- bsps/microblaze: Add support for multiple UARTs
- 04:43 Changeset in rtems [1fbfc4ee] by Maldonado, Sergio E. (GSFC-580.0) <sergio.e.maldonado@…>
- bsps/microblaze: Allow copying FDT from U-Boot
02/27/23:
- 21:49 Changeset in rtems [d5c386f] by Sebastian Huber <sebastian.huber@…>
- pps: Round to closest integer in pps_event() The comment above bintime2timespec() says: When converting between timestamps on parallel timescales of differing resolutions it is historical and scientific practice to round down. However, the delta_nsec value is a time difference and not a timestamp. Also the rounding errors accumulate in the frequency accumulator, see hardpps(). So, rounding to the closest integer is probably slightly better. Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/604
- 21:49 Changeset in rtems [d9f5345] by Sebastian Huber <sebastian.huber@…>
- pps: Simplify the nsec calculation in pps_event() Let A be the current calculation of the frequency accumulator (pps_fcount) update in pps_event() scale = (uint64_t)1 << 63; scale /= captc->tc_frequency; scale *= 2; bt.sec = 0; bt.frac = 0; bintime_addx(&bt, scale * tcount); bintime2timespec(&bt, &ts); hardpps(tsp, ts.tv_nsec + 1000000000 * ts.tv_sec); and hardpps(..., delta_nsec): u_nsec = delta_nsec; if (u_nsec > (NANOSECOND >> 1)) u_nsec -= NANOSECOND; else if (u_nsec < -(NANOSECOND >> 1)) u_nsec += NANOSECOND; pps_fcount += u_nsec; This change introduces a new calculation which is slightly simpler and more straight forward. Name it B. Consider the following sample values with a tcount of 2000000100 and a tc_frequency of 2000000000 (2GHz). For A, the scale is 9223372036. Then scale * tcount is 18446744994337203600 which is larger than UINT64_MAX (= 18446744073709551615). The result is 920627651984 == 18446744994337203600 % UINT64_MAX. Since all operands are unsigned the result is well defined through modulo arithmetic. The result of bintime2timespec(&bt, &ts) is 49. This is equal to the correct result 1000000049 % NANOSECOND. In hardpps(), both conditional statements are not executed and pps_fcount is incremented by 49. For the new calculation B, we have 1000000000 * tcount is 2000000100000000000 which is less than UINT64_MAX. This yields after the division with tc_frequency the correct result of 1000000050 for delta_nsec. In hardpps(), the first conditional statement is executed and pps_fcount is incremented by 50. This shows that both methods yield roughly the same results. However, method B is easier to understand and requires fewer conditional statements. Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/604
- 21:49 Changeset in rtems [3cda5ad9] by Sebastian Huber <sebastian.huber@…>
- pps: Directly assign the timestamps in pps_event() Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/604
- 21:49 Changeset in rtems [6730543] by Sebastian Huber <sebastian.huber@…>
- pps: Move pcount assignment in pps_event() Move the pseq increment. This makes it possible to reuse registers earlier. Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/604
- 21:49 Changeset in rtems [2a30bbf] by Sebastian Huber <sebastian.huber@…>
- pps: Simplify capture and event processing Use local variables for the captured timehand and timecounter in pps_event(). This fixes a potential issue in the nsec preparation for hardpps(). Here the timecounter was accessed through the captured timehand after the generation was checked. Make a snapshot of the relevent timehand values early in pps_event(). Check the timehand generation only once during the capture and event processing. Use atomic_thread_fence_acq() similar to the other readers. Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/604
- 21:49 Changeset in rtems [069275f5] by Sebastian Huber <sebastian.huber@…>
- pps: Load timecounter once in pps_capture() This ensures that the timecounter and the tc_get_timecount handler belong together. Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/604
- 16:22 Ticket #4666 (TFTP: Implement block and window size options) closed by Frank Kuehndel
- fixed
- 15:06 Developer/OpenProjects edited by Joel Sherrill
- (diff)
- 15:03 Ticket #4866 (Docs lie about default of riscv BSP_FDT_BLOB_SIZE_MAX) created by Jens Schweikhardt
- Chasing the reason for why a tiny RTEMS app is about 300KB in size, I …
- 06:34 Changeset in rtems [269562cf] by Sebastian Huber <sebastian.huber@…>
- bsps/riscv: Use medany cmodel for 64-bit variants Updates #4775.
02/26/23:
- 02:59 FundingProjects edited by Amar Takhar
- Expand project list tickets to be added in the future. (diff)
02/25/23:
- 10:37 Ticket #4865 (BSP support for LS1046 (NXP layerscape processor) ?) created by TRINATH KARRI
- Hi, Is there a BSP support for LS1046 (NXP layerscape processor) ? If …
02/24/23:
- 22:25 Changeset in rtems [d08dfc3] by Kinsey Moore <kinsey.moore@…>
- bsps/aarch64: Disable interrupts during MMU remap Interrupts must be disabled during MMU remapping since the majority of RTEMS including interrupts expects normal memory mapping semantics such as unaligned accesses.
- 07:44 Changeset in rtems-source-builder [bfed514] by Sebastian Huber <sebastian.huber@…>
- 6: Update GCC 10 and 12
- 07:43 Changeset in rtems-source-builder [fd4757d] by Sebastian Huber <sebastian.huber@…>
- 6/7: Update Newlib
02/23/23:
- 12:40 Ticket #4864 (Bitwise operator applied to a signed operand) created by Daniel Páscoa
- Bitwise operators should not be applied to signed operand. Most …
- 12:37 Ticket #4863 (Operations evaluation order.) created by Daniel Páscoa
- Within cpukit\include\rtems\score\objectimpl.h line 545 one has: if ( …
- 12:36 Ticket #4862 (score/ & bsps/: Unused input parameters) created by Daniel Páscoa
- The following functions list input parameters on their signature that …
02/22/23:
- 22:46 Changeset in rtems-lwip [cd9d9e7] by Kinsey Moore <kinsey.moore@…>
- lwip/sockets.h: Avoid duplication of system struct Excise another portion of lwIP's headers that redefine structures available from toolchain headers.
Note: See TracTimeline
for information about the timeline view.
