HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
atgreen
RTEMS
C2025–2025
atgreen / RTEMS

RTEMS

RTEMS

5Distinct people
5Mentions
0Explicit recommenders
10GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

RTEMS

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval5 dated mentions

Observed mentions: 2025-04-27 19:19:51 UTC to 2025-04-29 09:38:15 UTC.

0122025-04-27 18:00:00 UTC to 2025-04-27 21:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsApr 27, 18:002025-04-27 21:00:00 UTC to 2025-04-28 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-04-28 00:00:00 UTC to 2025-04-28 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-28 03:00:00 UTC to 2025-04-28 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-28 06:00:00 UTC to 2025-04-28 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-04-28 09:00:00 UTC to 2025-04-28 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-28 12:00:00 UTC to 2025-04-28 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 28, 12:002025-04-28 15:00:00 UTC to 2025-04-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-28 18:00:00 UTC to 2025-04-28 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-28 21:00:00 UTC to 2025-04-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-29 00:00:00 UTC to 2025-04-29 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-29 03:00:00 UTC to 2025-04-29 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-29 06:00:00 UTC to 2025-04-29 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-29 09:00:00 UTC to 2025-04-29 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 29, 09:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 27, 18:002025-04-27 18:00:00 UTC2025-04-27 21:00:00 UTC202
Apr 27, 21:002025-04-27 21:00:00 UTC2025-04-28 00:00:00 UTC101
Apr 28, 00:002025-04-28 00:00:00 UTC2025-04-28 03:00:00 UTC000
Apr 28, 03:002025-04-28 03:00:00 UTC2025-04-28 06:00:00 UTC000
Apr 28, 06:002025-04-28 06:00:00 UTC2025-04-28 09:00:00 UTC101
Apr 28, 09:002025-04-28 09:00:00 UTC2025-04-28 12:00:00 UTC000
Apr 28, 12:002025-04-28 12:00:00 UTC2025-04-28 15:00:00 UTC000
Apr 28, 15:002025-04-28 15:00:00 UTC2025-04-28 18:00:00 UTC000
Apr 28, 18:002025-04-28 18:00:00 UTC2025-04-28 21:00:00 UTC000
Apr 28, 21:002025-04-28 21:00:00 UTC2025-04-29 00:00:00 UTC000
Apr 29, 00:002025-04-29 00:00:00 UTC2025-04-29 03:00:00 UTC000
Apr 29, 03:002025-04-29 03:00:00 UTC2025-04-29 06:00:00 UTC000
Apr 29, 06:002025-04-29 06:00:00 UTC2025-04-29 09:00:00 UTC000
Apr 29, 09:002025-04-29 09:00:00 UTC2025-04-29 12:00:00 UTC101

What Hacker News says

1 sources
> The OP cites these (https://github.com/devkitPro/libogc/blob/52c525a13fd1762c103... and https://github.com/atgreen/RTEMS/blob/2f200c7e642c214accb7cc...), but that's hardly a smoking gun. The function is trivial, just filling in some struct fields. Yeah, I'm with Marcan 90% of the time, and in my view Marcan is more likely than not right that that function is derived from the RTEMS function, but in my view there's still reasonable doubt. That is to say, purely based on the evidence linked, I only agree that it's probable that the code is copied and disagree with Marcan's claim that it's "not possible" for the implementation to be non-infringing. The fact that some of the identifiers are similar raises the biggest suspicions. "__lwp_stack_isenough" vs. "_Stack_Is_enough" is suspicious because I'd probably call that "sufficient_stack_avail
Read the rest
able" or something like that. "LWP_STATES_DORMANT" vs. "STATES_DORMANT" is also suspicious because the normal OS term would be "sleeping". Still, the function logic is different enough that, even with that evidence, one could plausibly claim that only the headers or interface were copied and the implementation was clean-room, which is non-infringing per Oracle v. Google. In US legal system terms, I'd say that a preponderance of the evidence shows that the code is a derivative work (i.e. it's more likely than not that the code was copied at some point), but that there's still reasonable doubt (i.e. a reasonable person could plausibly believe otherwise).
In Libogc (Wii homebrew library) discovered to contain code stolen from RTEMS

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.