RTEMS / Documentation / Documentation¶
Go to Issues or Merge Requests
Issues Summary
Issues¶
18 - Checking if Sphinx is between 1.3 and 5.9¶
Id |
18 |
State |
closed |
Type |
ISSUE |
Author |
Sebastian Huber |
Closed by |
Sebastian Huber |
Created |
2024-07-03T18:55:35.260Z |
Closed |
2024-07-04T05:27:14.273Z |
Updated |
2024-07-04T05:28:23.881Z |
Milestone |
6.1 |
Labels |
doc::sphinx |
Link |
|
Merges |
0 |
Summary¶
I naively installed Sphinx through pip in a virtual environment and got:
Checking if Sphinx is between 1.3 and 5.9 : Sphinx version is too new: 7.3
Is this version limitation still applicable?
Author: Joel Sherrill
2024-07-03T22:42:14.934Z
Weird. I use the sphinx provided with Rocky 9 and it reports “sphinx-build 7.2.6.” I do not seem to be tripping that.
And I do not see “is between 1.3” when I grep rtems-docs. common/waf.py has this:
# If you do not want to check for a maximum version, set it to None.
sphinx_min_version = (1, 3)
sphinx_max_version = NoneAre you up to date?
Author: Chris Johns
2024-07-03T22:42:14.906Z
Where is there a need to cap the version at 5.9?
Author: Amar Takhar
2024-07-03T22:18:29.437Z
I forget what broke in Sphinx however I am re-working the build system for the documentation to allow individual docs to build again and fix some things that were broken as well as bring us up to date.
You can target a specific version with:
pip install sphinx==5.3.0You can remove it first and re-install. I do not think it’s worth updating yet because as far as I know the rendering issues have not been resolved.
Author: Chris Johns
2024-07-03T22:48:37.244Z
I am using 7.3.7. My configure is:
Setting top to : /opt/work/chris/rtems/docs/rtems-docs.git Setting out to : /opt/work/chris/rtems/docs/rtems-docs.git/build Checking for program 'git' : /usr/local/bin/git Checking for program 'sphinx-build' : /opt/work/chris/rtems/r-py-3/bin/sphinx-build Checking for program 'aspell' : not found Checking if Sphinx is at least 1.3 : yes (7.3) Checking Sphinx Options : none Checking Sphinx Nit-Pick mode : no Checking for 'sphinx-rtd-theme' : found Checking for 'sphinx.ext.autodoc' : found Checking for 'sphinx.ext.coverage' : found Checking for 'sphinx.ext.doctest' : found Checking for 'sphinx.ext.graphviz' : found Checking for 'sphinx.ext.intersphinx' : found Checking for 'sphinx.ext.mathjax' : found Checking for 'sphinxcontrib.bibtex' : found Checking for 'sphinxcontrib.jquery' : foundThe build result is:
Waf: Leaving directory `/opt/work/chris/rtems/docs/rtems-docs.git/build' 'build' finished successfully (42.631s)Host:
FreeBSD torea 14.0-RELEASE FreeBSD 14.0-RELEASE #0 releng/14.0-n265380-f9716eee8ab4: Fri Nov 10 05:57:23 UTC 2023 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64I am not sure what the issue is?
Author: Amar Takhar
2024-07-03T22:48:37.217Z
No idea I just remember the latest version breaking the theme some time ago and it was capped? Was that fixed?
Author: Chris Johns
2024-07-03T22:49:16.982Z
Yes
Author: Chris Johns
2024-07-03T22:52:00.753Z
After reading the question in the description by @sebhub I see this is a question and not a problem. @sebhub no it should not be a problem. Where is the limit stated?
Author: Sebastian Huber
2024-07-04T05:28:23.896Z
Sorry for the trouble, this was caused by a configuration error on my side. The rtems-docs submodule in rtems-central is pretty outdated right now.
Author: Chris Johns
2024-07-04T05:28:23.863Z
No problem and thanks for the update.
14 - Update POSIX Compliance Guide for New Standards Editions¶
Id |
14 |
State |
closed |
Type |
ISSUE |
Author |
Joel Sherrill |
Assignee(s) |
Joel Sherrill |
Closed by |
Kinsey Moore |
Created |
2024-06-14T17:12:11.774Z |
Closed |
2024-06-18T01:46:14.969Z |
Updated |
2024-06-18T01:46:15.410Z |
Milestone |
6.1 |
Labels |
posix::compliance |
Link |
|
Merges |
1 |
Summary¶
The POSIX Compliance Guide is based on a spreadsheet which has not been updated in a few years. The FACE Technical Standard, Edition 3.2 and C17 both need to be added. Also there are improvements to RTEMS which need to be accounted for.
Steps to reproduce¶
Author: Joel Sherrill
2024-06-14T17:12:11.855Z
assigned to @joel
Author: Joel Sherrill
2024-06-14T17:14:01.064Z
mentioned in merge request !19
8 - Document Merge Request Workflow¶
Id |
8 |
State |
closed |
Type |
ISSUE |
Author |
Chris Johns |
Closed by |
Amar Takhar |
Created |
2024-05-02T22:44:58.978Z |
Closed |
2024-05-18T04:02:23.469Z |
Updated |
2024-05-22T21:41:29.400Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
1 |
Document Merge Request Workflow¶
Document how to add comments to specific lines that are being reviewed or adding a comment to the top level
When you a merge request you land on the page with all the comments and you need to find the specific area you wish to comment on.
How to update a Merge Request with changes
Make a draft merge request if you want to review it first or it is a RFC
Consider using the quick commands accessed using
?
Author: Chris Johns
2024-05-02T23:34:22.366Z
marked this issue as related to #9
Author: Gedare Bloom
2024-05-16T16:53:36.385Z
mentioned in merge request !10
Author: Gedare Bloom
2024-05-22T21:41:29.379Z
mentioned in issue administration/gitlab#11
5 - Contributing guidance is outdated¶
Id |
5 |
State |
closed |
Type |
ISSUE |
Author |
Gedare Bloom |
Assignee(s) |
Gedare Bloom |
Closed by |
Gedare Bloom |
Created |
2024-04-29T17:46:24.755Z |
Closed |
2024-05-02T04:59:46.379Z |
Updated |
2024-05-22T21:41:29.368Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
2 |
Summary¶
Contribution guidance needs to be updated for using Gitlab.
Steps to reproduce¶
Author: Gedare Bloom
2024-04-29T17:46:24.839Z
assigned to @gedare
Author: Gedare Bloom
2024-04-29T17:46:30.433Z
created branch 5-contributing-guidance-is-outdated to address this issue
Author: Gedare Bloom
2024-04-29T17:47:04.582Z
mentioned in merge request !4
Author: Gedare Bloom
2024-05-01T15:22:36.801Z
mentioned in merge request !5
Author: Gedare Bloom
2024-05-22T21:41:29.340Z
mentioned in issue administration/gitlab#11
4 - Rewrite bug user story¶
Id |
4 |
State |
closed |
Type |
ISSUE |
Author |
Gedare Bloom |
Assignee(s) |
Gedare Bloom |
Closed by |
Gedare Bloom |
Created |
2024-04-29T17:17:49.690Z |
Closed |
2024-04-30T15:09:02.707Z |
Updated |
2024-05-22T21:41:29.129Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
1 |
Summary¶
Update guidance for how user’s should submit bug reports to Gitlab
Steps to reproduce¶
Author: Gedare Bloom
2024-04-29T17:17:49.773Z
assigned to @gedare
Author: Gedare Bloom
2024-04-29T17:17:55.416Z
created branch 4-rewrite-bug-user-story to address this issue
Author: Gedare Bloom
2024-04-29T17:19:05.353Z
mentioned in merge request !3
Author: Gedare Bloom
2024-05-22T21:41:29.056Z
mentioned in issue administration/gitlab#11
10 - Manuals refer to git.rtems.org¶
Id |
10 |
State |
closed |
Type |
ISSUE |
Author |
Gedare Bloom |
Assignee(s) |
Gedare Bloom |
Closed by |
Amar Takhar |
Created |
2024-05-16T18:45:00.248Z |
Closed |
2024-05-18T04:03:52.361Z |
Updated |
2024-05-18T04:03:52.429Z |
Milestone |
6.1 |
Link |
|
Merges |
1 |
Summary¶
Several of the manuals have references to git.rtems.org URLs that should be updated to gitlab.rtems.org
Steps to reproduce¶
Author: Gedare Bloom
2024-05-16T18:45:00.323Z
assigned to @gedare
Author: Gedare Bloom
2024-05-16T19:12:28.996Z
mentioned in merge request !11
2 - Rewrite trac links to gitlab¶
Id |
2 |
State |
closed |
Type |
ISSUE |
Author |
Gedare Bloom |
Assignee(s) |
Gedare Bloom |
Closed by |
Gedare Bloom |
Created |
2024-04-29T14:58:32.944Z |
Closed |
2024-04-29T20:14:47.535Z |
Updated |
2024-04-29T20:14:47.579Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
1 |
Summary¶
Reflect Trac to Gitlab migration
Steps to reproduce¶
Author: Gedare Bloom
2024-04-29T14:58:33.051Z
assigned to @gedare
Author: Gedare Bloom
2024-04-29T14:58:42.169Z
created branch 2-rewrite-trac-links-to-gitlab to address this issue
Author: Gedare Bloom
2024-04-29T14:59:26.808Z
mentioned in merge request !1
3 - sync git.rtems.org¶
Id |
3 |
State |
closed |
Type |
ISSUE |
Author |
Gedare Bloom |
Assignee(s) |
Gedare Bloom |
Closed by |
Gedare Bloom |
Created |
2024-04-29T15:08:46.739Z |
Closed |
2024-04-29T20:13:42.555Z |
Updated |
2024-04-29T20:13:42.653Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
1 |
Summary¶
pull commits from git.rtems.org lost by transition
Steps to reproduce¶
Author: Gedare Bloom
2024-04-29T15:08:46.846Z
assigned to @gedare
Author: Gedare Bloom
2024-04-29T15:09:04.491Z
created branch 3-sync-git-rtems-org to address this issue
Author: Gedare Bloom
2024-04-29T15:09:26.055Z
mentioned in merge request !2
21 - Create a contributor section in the RTEMS Documentation. (opened)¶
Id |
21 |
State |
opened |
Type |
ISSUE |
Author |
Amar Takhar |
Created |
2024-07-26T01:46:51.461Z |
Updated |
2024-07-30T05:02:23.137Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
Summary¶
We need to have a giant list of those who have contributed to RTEMS like most projects maintain. We have some users in the RTEMS MAINTAINERS file plus many more that have contributed but are listed nowhere.
It would be great to have this for %6.1 so it makes it into the release we can take it from the commit history in Git.
Here is the old MAINTAINERS file:
This file will need to be included here as well:
Author: Amar Takhar
2024-07-26T01:55:15.310Z
mentioned in commit amar/rtems@2afa55270c58423b228017313c0b42d9190c4e96
Author: Amar Takhar
2024-07-26T20:23:00.233Z
mentioned in commit amar/rtems@2ba94118a0867a1cae543af7d85603d8074cd6c6
Author: Amar Takhar
2024-07-28T22:24:04.076Z
changed the description
Author: Amar Takhar
2024-07-28T22:26:36.410Z
mentioned in commit amar/rtems@538e8190336f8490f51420749954d04aa8c70c24
Author: Amar Takhar
2024-07-28T22:27:35.210Z
mentioned in merge request rtems/rtos/rtems!142
Author: Amar Takhar
2024-07-30T05:02:22.981Z
mentioned in commit amar/rtems@ed0afd723999e13390bb3f4bc3742339a222f38c
28 - Add Filesystem Documentation to User’s Guide with limitations (opened)¶
Id |
28 |
State |
opened |
Type |
ISSUE |
Author |
Kinsey Moore |
Created |
2024-07-29T21:55:14.434Z |
Updated |
2024-07-29T21:57:35.597Z |
Milestone |
6.1 |
Labels |
filesystem |
Link |
|
Merges |
0 |
Summary¶
The RTEMS User’s Guide needs a filesystems section that describes the limitations of the various filesystems RTEMS supports in their current state.
JFFS2¶
The JFFS2 implementation in RTEMS supports operation on NOR and NAND, but does not yet support Erase Block Summary (EBS) on NAND which affects mount times for large, full filesystems. JFFS2 has a maximum filesystem size of 4GB-1 block. JFFS2 uses 32-bit time in the on-disk format and is not Y2038-safe. JFFS2 read/write performance degrade when full.
MSDOS¶
MSDOS uses 32-bit time in the on-disk format and is not Y2038-safe. The maximum file size is 4GB. There are limits on the accuracy of timestamps (1s granularity). Symlinks are not supported.
Author: Kinsey Moore
2024-07-29T21:57:35.667Z
changed the description
24 - Depreciating Interfaces needs moving from wiki (opened)¶
Id |
24 |
State |
opened |
Type |
ISSUE |
Author |
Amar Takhar |
Created |
2024-07-26T23:39:08.220Z |
Updated |
2024-07-28T12:11:23.564Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
Summary¶
This file:
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/blob/main/eng/coding-deprecating.rst?ref_type=heads
Needs to be populated by the contents of this file:
Needs to be done before %6.1 as part of devel.rtems.org decomissioning.
Steps to reproduce¶
Author: Amar Takhar
2024-07-27T00:06:30.797Z
changed title from Deprec{-t-}ating Interfaces needs moving from wiki to Deprec{+i+}ating Interfaces needs moving from wiki
Author: Amar Takhar
2024-07-27T00:07:02.295Z
mentioned in merge request !38
Author: Amar Takhar
2024-07-28T12:11:23.428Z
mentioned in commit 05f9a3d56b45e700104d22bf40881ef89fff5d91
25 - Move example file from old wiki into docs. (opened)¶
Id |
25 |
State |
opened |
Type |
ISSUE |
Author |
Amar Takhar |
Assignee(s) |
Chris Johns |
Created |
2024-07-26T23:43:01.614Z |
Updated |
2024-07-28T12:11:23.367Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
Summary¶
The example file located at:
Needs a new location, it’s small why not inline it in the docs so someone could copy and paste?
Here is the file:
Steps to reproduce¶
Author: Amar Takhar
2024-07-26T23:43:01.800Z
assigned to @chris
Author: Amar Takhar
2024-07-26T23:43:14.272Z
Assigned this to @chris since he made that file.
Author: Amar Takhar
2024-07-27T00:10:33.040Z
mentioned in merge request !38
Author: Amar Takhar
2024-07-28T12:11:23.265Z
mentioned in commit 05f9a3d56b45e700104d22bf40881ef89fff5d91
26 - Import old wiki pages into Coding Conventions (opened)¶
Id |
26 |
State |
opened |
Type |
ISSUE |
Author |
Amar Takhar |
Created |
2024-07-27T00:04:13.215Z |
Updated |
2024-07-28T12:11:23.105Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
Summary¶
This file:
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/blob/main/eng/coding-conventions.rst?ref_type=heads
Contains far too many references to the old wiki the content needs to be brought into the docs themselves.
The pages can be found here:
Steps to reproduce¶
Author: Amar Takhar
2024-07-27T00:06:14.648Z
changed title from Import old wiki pages into Coding Convent{-at-}ions to Import old wiki pages into Coding Conventions
Author: Amar Takhar
2024-07-27T00:07:02.261Z
mentioned in merge request !38
Author: Amar Takhar
2024-07-28T12:11:22.857Z
mentioned in commit 05f9a3d56b45e700104d22bf40881ef89fff5d91
27 - Follow-up from “Remove old references to devel.rtems.org” (opened)¶
Id |
27 |
State |
opened |
Type |
ISSUE |
Author |
Amar Takhar |
Assignee(s) |
Joel Sherrill |
Created |
2024-07-28T04:48:38.181Z |
Updated |
2024-07-28T04:48:38.181Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
The following discussion from !38 should be addressed:
[] @joel started a discussion:
Turn reviewing this into an issue and assign it to me. I think this is at least an unfair or out of date statement
The diff:
Author: Amar Takhar
2024-07-28T04:48:38.299Z
assigned to @joel
22 - Link to non exisent repository (opened)¶
Id |
22 |
State |
opened |
Type |
ISSUE |
Author |
Amar Takhar |
Assignee(s) |
Sebastian Huber |
Created |
2024-07-26T19:07:12.554Z |
Updated |
2024-07-26T19:07:12.554Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
Summary¶
There is a link to a non existent repository here:
@sebhub , what is going on with this repo? Thanks.
Steps to reproduce¶
Author: Amar Takhar
2024-07-26T19:07:12.744Z
assigned to @sebhub
19 - Document keeping mirrors updated (opened)¶
Id |
19 |
State |
opened |
Type |
ISSUE |
Author |
Amar Takhar |
Assignee(s) |
Amar Takhar, Chris Johns, Gedare Bloom |
Created |
2024-07-15T17:52:14.772Z |
Updated |
2024-07-20T21:29:43.145Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
Summary¶
Keeping forked repos and branches within those repos is a real pain and can be easily forgotten.
GitLab allows the ability – which the RTEMS Project has enabled the feature of repository mirroring it does increase load to the instance however.
With this you can automatically keep your forks updated. RTEMS does not allow direct pushing to repositories so the flow is always:
graph TD
A(RTEMS Repository)
-->B(Repository Mirroring)
-->C[/Forked Repository\\]
The branches you keep on your forked repo will remain intact but your forked repo will always be up-to-date.
@chris made a summary of what to do on ``#gitlab-support`` on Discord.
Select the fork in your personal area
Left side at the bottom select Settings then Repository
Expand Mirroring Repositories then click Add
The Repository URL is the upstream repo’s HTTPS Code button URL
Select Pull and leave the Username and Password empty.
Click Mirror Repository
7. Go into Protected branches
1. Set Allowed to push and merge to No one This will ensure you don’t accidentally push to your main branch on a personal repo.
Notes¶
Please do not mirror repositories that are not on our GitLab instance without asking in
#gitlab-supportYou can mirror a single branch from a repository in fact you can mirror from several different upstream branches onto a single repository.
Steps to reproduce¶
Author: Amar Takhar
2024-07-15T17:52:14.976Z
assigned to @gedare, @chris, and @amar
Author: Amar Takhar
2024-07-15T19:08:08.010Z
changed the description
Author: Amar Takhar
2024-07-20T21:29:43.289Z
changed the description
Author: Amar Takhar
2024-07-20T21:30:36.904Z
Added a note about disabling push abilities to
mainon a personal repo. This happened to me just now and it’s a pain to fix since you have to enable force push. Since we’re already there adding the mirror it’s better to disable it.
20 - Create a process on when to create an issue vs MR vs both. (opened)¶
Id |
20 |
State |
opened |
Type |
ISSUE |
Author |
Amar Takhar |
Created |
2024-07-20T20:29:26.393Z |
Updated |
2024-07-20T20:29:50.844Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
Summary¶
We don’t have any formal documentation about when an issue should be created. My proposal is to follow these two simple rules:
If you need design and discussion before opening an MR create an issue.
If you wish to collect multiple MRs for tracking create an issue or even better an epic.
Issues / tickets were important in the past because it allowed for tracking details related to a change.
MRs allow for inline commenting on patches and are threaded which makes for better engineering conversation especially with the code and iterative changes being possible.
What we do lose by not having issues:
It’s harder to track a change in git back to the MR because
git logdoes not show the reverse connection.This is not a great solution as we’ve already lost track of some of these numbers see below.
A solution to the above problem is to annotate commits using git note. These do not change commit hashes and are stored out of band. It also does not come up unless you explicitly look for the note so we can add whatever information we like here. If we ever migrate off of GitLab we can change these notes to point to whatever new platform we choose.
We already have the problem where issue numbers are different and over time if we are unable to keep the numbers the same these will lose meaning. Git notes are freely modifiable and do not suffer from this problem.
@chris @gedare @opticron @joel
9 - Document Project Workflow (opened)¶
Id |
9 |
State |
opened |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Gedare Bloom |
Created |
2024-05-02T23:32:32.936Z |
Updated |
2024-05-26T00:04:14.164Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
Document Project Workflow¶
Populate what use to be Git Users with tutorials and strategies for: 1. Submitters 2. Approvers 3. Reviewers 4. Code owners
Highlight your projects by staring the project and then configure your home page in your profile to show starred projects
Searches will be remembered in the Issues search bar by clicking on the left box and it should list your previous searches.
Author: Chris Johns
2024-05-02T23:32:33.052Z
assigned to @gedare
Author: Chris Johns
2024-05-02T23:33:44.974Z
Not all users will appear in the Edit boxes. Add the user by a @user in a comment, refresh your browser and then you can edit the assignee.
Author: Chris Johns
2024-05-02T23:34:22.337Z
marked this issue as related to #8
Author: Gedare Bloom
2024-05-03T19:53:18.672Z
Document COI rules for explicit code owners
Author: Gedare Bloom
2024-05-03T19:57:54.615Z
@gedare do it!
Author: Gedare Bloom
2024-05-22T21:41:29.411Z
mentioned in issue administration/gitlab#11
Author: Amar Takhar
2024-05-26T00:04:13.771Z
A note about ‘Draft’ MRs. These should be created in two situations:
As a submitter your MR isn’t ready for a full review but you want one or multiple developers to look at it. This avoids churn when everyone looks at an MR that is not ready for wide review.
An already submitted MR needs a lot of work but more importantly needs to be blocked from being merged. Once it is un-drafted it can be open for wide review. Again to avoid churn see https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/42#note_106339 as an example.
Draft MRs are a useful tool in both cases as it can allow for a little development on-the-spot rather than doing it in a branch if it’s not something large.
11 - Mention GitLab in user/migration/v5-to-v6.rst (opened)¶
Id |
11 |
State |
opened |
Type |
ISSUE |
Author |
Gedare Bloom |
Created |
2024-05-16T19:16:09.288Z |
Updated |
2024-05-16T19:16:09.288Z |
Milestone |
6.1 |
Labels |
infra::migration |
Link |
|
Merges |
0 |
Summary¶
During the v6 release we have transitioned to GitLab. It should be mentioned in the migration notes.
Steps to reproduce¶
7 - Document Labels in the Engineering Manual (opened)¶
Id |
7 |
State |
opened |
Type |
ISSUE |
Author |
Chris Johns |
Assignee(s) |
Gedare Bloom |
Created |
2024-05-02T22:16:15.718Z |
Updated |
2024-05-03T04:29:58.950Z |
Milestone |
6.1 |
Labels |
doc |
Link |
|
Merges |
0 |
Document Labels in the Engineering Manual¶
Add documentation about labels
Document the flow around subscribing to a label
Encourage users to select a label and assign it to Issues and Merge Requests
Author: Chris Johns
2024-05-02T22:16:15.805Z
assigned to @gedare
Merge Requests¶
38 - Remove old references to devel.rtems.org¶
Id |
38 |
State |
merged |
Merged by |
Joel Sherrill |
Merged at |
2024-07-28T12:11:21.549Z |
Created |
2024-07-27T00:06:58.274Z |
Updated |
2024-07-28T12:11:23.111Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/38 |
Commit |
Summary¶
Remove old references to devel.rtems.org
Some were deleted as the content was imported.
Other references were updated.
There is content that still needs to be imported and I have opened issues to handle this:
26 Import old wiki pages into Coding Conventions¶
25 Move example file from old wiki into docs.¶
24 Depreciating Interfaces needs moving from wiki¶
Author: Amar Takhar
2024-07-27T00:09:45.786Z
added 1 commit
05f9a3d5 - Remove old references to devel.rtems.org
Author: Amar Takhar
2024-07-27T00:10:32.967Z
changed the description
Author: Joel Sherrill
2024-07-28T12:10:15.376Z
Deleting this would lose the idea that something needs to be done. I think this info is in the software engineering guide so reference it instead.
Author: Amar Takhar
2024-07-28T12:10:15.376Z
I removed it because the content was imported it wasn’t? I’ll check again thanks
Author: Amar Takhar
2024-07-28T12:10:15.376Z
Yes the content of that file is from the wiki .. not sure what you’re asking here? Someone has already done the transition but forgot to remove the comment. Am I missing something?
Author: Joel Sherrill
2024-07-28T04:48:38.342Z
Turn reviewing this into an issue and assign it to me. I think this is at least an unfair or out of date statement
Author: Amar Takhar
2024-07-28T04:48:38.590Z
created #27 to continue this discussion
Author: Joel Sherrill
2024-07-28T04:15:16.390Z
requested changes
Author: Amar Takhar
2024-07-28T04:48:38.597Z
mentioned in issue #27
Author: Joel Sherrill
2024-07-28T12:10:15.396Z
resolved all threads
Author: Joel Sherrill
2024-07-28T12:11:17.126Z
approved this merge request
37 - Update old git.rtems.org links to GitLab¶
Id |
37 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2024-07-26T19:36:09.219Z |
Assignee(s) |
Amar Takhar |
Created |
2024-07-26T19:23:08.843Z |
Updated |
2024-07-26T19:48:05.328Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/37 |
Commit |
Summary¶
Update old git.rtems.org links to GitLab
Some console output I updated to to just be gitlab.rtems.org. I doubt anyone would notice but any references to git.rtems.org aren’t good.
Author: Amar Takhar
2024-07-26T19:23:08.998Z
assigned to @amar
Author: Amar Takhar
2024-07-26T19:23:32.600Z
Note this MR has a dependency.
Author: Kinsey Moore
2024-07-26T19:32:53.055Z
added 4 commits
2cc38939…03a27eed - 3 commits from branch
rtems/docs:maindd440be7 - Update old git.rtems.org links to GitLab
Author: Kinsey Moore
2024-07-26T19:35:59.169Z
approved this merge request
Author: Joel Sherrill
2024-07-26T19:48:05.977Z
The site review.rtems.org does not exist. I don’t know why this was ever here. Can it be deleted in this pass?
Author: Amar Takhar
2024-07-26T19:48:05.977Z
It’s not used anywhere it’ll be killed eventually not working on content with these changes.
Author: Joel Sherrill
2024-07-26T19:47:22.637Z
Does this need to point somewhere else?
Author: Amar Takhar
2024-07-26T19:47:22.637Z
Not working on fixing content these are something Gedare is working on.
Author: Joel Sherrill
2024-07-26T19:47:18.719Z
Both of these are deadends also
Author: Amar Takhar
2024-07-26T19:47:18.719Z
Not working on fixing content these are something Gedare is working on.
Author: Joel Sherrill
2024-07-26T19:46:57.366Z
This probably should be closed with an issue to update this to use gitlab processes.
Author: Amar Takhar
2024-07-26T19:46:57.366Z
That is under @gedare I’m not updating any of these docs.
Author: Joel Sherrill
2024-07-26T19:37:22.387Z
Feel free to resolve with an issue as appropriate. Gedare was supposed to be addressing development process documentation changes so assign to him where applicable.
Author: Amar Takhar
2024-07-26T19:48:05.999Z
resolved all threads
36 - Update source browser URLs to GitLab¶
Id |
36 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2024-07-26T19:32:39.307Z |
Assignee(s) |
Amar Takhar |
Created |
2024-07-26T18:43:28.925Z |
Updated |
2024-07-26T19:32:40.966Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/36 |
Commit |
Summary¶
Author: Amar Takhar
2024-07-26T18:43:29.078Z
assigned to @amar
Author: Kinsey Moore
2024-07-26T19:32:26.986Z
added 3 commits
5512eb3f…3ce7a357 - 2 commits from branch
rtems/docs:main03a27eed - Update source browser URLs to GitLab
Author: Kinsey Moore
2024-07-26T19:32:33.770Z
approved this merge request
35 - Point to new LICENSE.md¶
Id |
35 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2024-07-26T19:29:41.129Z |
Assignee(s) |
Amar Takhar |
Created |
2024-07-26T18:24:35.245Z |
Updated |
2024-07-26T19:29:42.403Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/35 |
Commit |
Summary¶
Point to new LICENSE.md
I didn’t link directly to the licenses as we’ll be moving the file around and there is a TOC. The less anchors the better any explanations should happen in the LICENSE.md file.
Author: Amar Takhar
2024-07-26T18:24:35.389Z
assigned to @amar
Author: Kinsey Moore
2024-07-26T19:29:12.626Z
approved this merge request
Author: Kinsey Moore
2024-07-26T19:29:26.819Z
added 2 commits
39ef1665 - 1 commit from branch
rtems/docs:main3ce7a357 - Point to new LICENSE.md
34 - Remove mention of MAINTAINERS file¶
Id |
34 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2024-07-26T19:28:55.463Z |
Assignee(s) |
Amar Takhar |
Created |
2024-07-26T18:19:28.921Z |
Updated |
2024-07-26T19:28:57.631Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/34 |
Commit |
Summary¶
Remove mention of MAINTAINERS file
See rtems/rtos/rtems!131
Author: Amar Takhar
2024-07-26T18:19:29.114Z
assigned to @amar
Author: Kinsey Moore
2024-07-26T19:28:52.426Z
approved this merge request
33 - Convert LICENSE file to MarkDown¶
Id |
33 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2024-07-25T22:15:53.833Z |
Assignee(s) |
Amar Takhar |
Created |
2024-07-20T04:56:24.384Z |
Updated |
2024-07-25T22:15:55.937Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/33 |
Commit |
Summary¶
Author: Amar Takhar
2024-07-20T04:56:24.937Z
assigned to @amar
Author: Joel Sherrill
2024-07-24T18:14:47.084Z
This is probably “resolve by filing issue”. Do we want the headings to be the real name of the license? Include an SPDX tag in the section? The anchor could be the SPDX name.
Author: Amar Takhar
2024-07-24T18:15:38.857Z
When I convert documentation I don’t make changes to the documentation at the same time. That way you can track old to new. If we want to change contents we should do that after it’s been converted. I do make some changes when the old content is really bad but titles I keep the same so the old ‘License 2’ can be tracked to its new place and then we can change it.
Author: Amar Takhar
2024-07-24T18:14:47.110Z
resolved all threads
Author: Kinsey Moore
2024-07-25T22:15:50.163Z
approved this merge request
32 - user/stm32h7: Separate comment block¶
Id |
32 |
State |
merged |
Merged by |
Gedare Bloom |
Merged at |
2024-07-18T20:52:25.517Z |
Assignee(s) |
Kinsey Moore |
Created |
2024-07-18T18:14:35.327Z |
Updated |
2024-07-18T20:52:27.021Z |
Milestone |
6.1 |
Labels |
arch:arm, doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/32 |
Commit |
Summary¶
user/stm32h7: Separate comment block
The comment blocks at the end of the console section are being rendered since they are not appropriately separated from the text block. This change prevents them from rendering as was intended.
Author: Kinsey Moore
2024-07-18T18:14:35.501Z
assigned to @opticron
Author: Gedare Bloom
2024-07-18T20:52:19.212Z
approved this merge request
29 - user: Swap to https from ssh¶
Id |
29 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2024-07-08T16:00:22.217Z |
Assignee(s) |
Kinsey Moore |
Created |
2024-07-08T15:56:46.442Z |
Updated |
2024-07-08T16:00:23.638Z |
Milestone |
6.1 |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/29 |
Commit |
Summary¶
user: Swap to https from ssh
Users running through the getting started process won’t be likely to have a GitLab account and so SSH access is out of reach for them. This changes all new-user-facing repository clones to HTTP to avoid issues in this process.
Author: Kinsey Moore
2024-07-08T15:56:46.594Z
assigned to @opticron
Author: Amar Takhar
2024-07-08T16:00:12.624Z
Adding @gedare so he is away it’s been changed.
Author: Amar Takhar
2024-07-08T16:00:15.596Z
approved this merge request
27 - posix-compliance: Update tracking CSV for published POSIX-2024 (Issue 8)¶
Id |
27 |
State |
merged |
Merged by |
Chris Johns |
Merged at |
2024-07-02T01:49:15.101Z |
Assignee(s) |
Joel Sherrill |
Reviewer(s) |
Gedare Bloom |
Created |
2024-07-01T18:45:02.291Z |
Updated |
2024-07-02T01:49:17.326Z |
Milestone |
6.1 |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/27 |
Commit |
Summary¶
POSIX-2024 (Issue 8) was recently published. The information in that column was double-checked versus the published edition.
RTEMS support for new Issue 8 functions was checked.
standards.rst was updated to mention Issue 8 and use the word function not method.
Author: Joel Sherrill
2024-07-01T18:45:02.420Z
requested review from @gedare
Author: Joel Sherrill
2024-07-01T18:45:03.378Z
assigned to @joel
Author: Amar Takhar
2024-07-01T18:49:53.556Z
added 13 commits
bce15fb7…9cc4ac74 - 12 commits from branch
rtems/docs:main9063fb34 - posix-compliance: Update API spreadsheet
Author: Joel Sherrill
2024-07-01T19:51:39.438Z
added 1 commit
7b3db9d6 - posix-compliance: Update API spreadsheet
Author: Chris Johns
2024-07-02T01:49:09.742Z
approved this merge request
19 - posix-compliance: Update tracking CSV and standards descriptions¶
Id |
19 |
State |
merged |
Merged by |
Kinsey Moore |
Merged at |
2024-06-18T01:46:14.674Z |
Assignee(s) |
Joel Sherrill |
Reviewer(s) |
Chris Johns, Gedare Bloom |
Created |
2024-06-14T17:13:56.561Z |
Updated |
2024-06-18T01:46:17.604Z |
Milestone |
6.1 |
Labels |
posix::compliance |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/19 |
Commit |
Summary¶
posix-compliance: Update tracking CSV and standards descriptions
Adds C17, FACE Technical Standard, Edition 3.2 and includes various updates to RTEMS support.
Closes #14
Author: Joel Sherrill
2024-06-14T17:13:56.688Z
requested review from @chris and @gedare
Author: Joel Sherrill
2024-06-14T17:13:56.703Z
assigned to @joel
Author: Gedare Bloom
2024-06-17T20:39:21.390Z
added 1 commit
2dde95b6 - standards.rst: fix typo
Author: Gedare Bloom
2024-06-17T20:39:50.760Z
approved this merge request
Author: Gedare Bloom
2024-06-17T20:40:16.598Z
added 4 commits
2dde95b6…ae3d5cfc - 2 commits from branch
rtems/docs:main6a2d014e - posix-compliance: Update tracking CSV and standards descriptions
05d72243 - standards.rst: fix typo
16 - user/testing: Update documentation for RTEMS 6¶
Id |
16 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2024-06-08T00:52:21.571Z |
Assignee(s) |
Kinsey Moore |
Created |
2024-06-07T02:57:02.486Z |
Updated |
2024-06-08T00:52:22.670Z |
Milestone |
6.1 |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/16 |
Commit |
Summary¶
Updates https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/4960
Author: Kinsey Moore
2024-06-07T02:57:02.645Z
assigned to @opticron
Author: Kinsey Moore
2024-06-07T02:57:22.969Z
added 6 commits
d740bc4a…d196c8bc - 5 commits from branch
rtems/docs:main989e939d - user/testing: Update documentation for RTEMS 6
Author: Gedare Bloom
2024-06-07T22:20:32.362Z
approved this merge request
8 - c-user: Document get/set interrupt priority¶
Id |
8 |
State |
merged |
Merged by |
Chris Johns |
Merged at |
2024-05-28T21:20:40.931Z |
Created |
2024-05-02T14:02:35.000Z |
Updated |
2024-05-28T21:20:42.483Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/8 |
Commit |
Summary¶
Update #5002.
Author: Sebastian Huber
2024-05-08T07:43:12.856Z
added 1 commit
a72be6ec - c-user: Document get/set interrupt priority
Author: Chris Johns
2024-05-25T08:50:05.113Z
Is this the state for not supported by the processor? This is not mentioned and I think it is important to mention.
Author: Sebastian Huber
2024-05-25T08:50:05.113Z
This text is basically the same for all interrupt vector related functions. If it is not clear, then we should find a better standard text for this error.
Author: Chris Johns
2024-05-25T08:50:05.113Z
I am not sure how that relates? Are you saying all interrupts calls a required to return a specific error code for the exact same reasons?
Author: Sebastian Huber
2024-05-25T08:50:05.113Z
Yes, for the RTEMS_INVALID_ID, there is a common text:
grep -rn RTEMS_INVALID_ID c-user/interrupt/ -A 2 c-user/interrupt/directives.rst:1230::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1231- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1232- ``vector``. -- c-user/interrupt/directives.rst:1319::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1320- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1321- ``vector``. -- c-user/interrupt/directives.rst:1440::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1441- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1442- ``vector``. -- c-user/interrupt/directives.rst:1527::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1528- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1529- ``vector``. -- c-user/interrupt/directives.rst:1601::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1602- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1603- ``vector``. -- c-user/interrupt/directives.rst:1661::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1662- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1663- ``vector``. -- c-user/interrupt/directives.rst:1723::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1724- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1725- ``vector``. -- c-user/interrupt/directives.rst:1802::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1803- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1804- ``vector``. -- c-user/interrupt/directives.rst:1859::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1860- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1861- ``vector``. -- c-user/interrupt/directives.rst:1921::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1922- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1923- ``vector``. -- c-user/interrupt/directives.rst:1984::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-1985- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-1986- ``vector``. -- c-user/interrupt/directives.rst:2058::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2059- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-2060- ``vector``. -- c-user/interrupt/directives.rst:2128::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2129- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-2130- ``vector``. -- c-user/interrupt/directives.rst:2206::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2207- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-2208- ``vector``. -- c-user/interrupt/directives.rst:2276::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2277- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-2278- ``vector``. -- c-user/interrupt/directives.rst:2522::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2523- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-2524- ``server_index``. -- c-user/interrupt/directives.rst:2533::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2534- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-2535- ``vector``. -- c-user/interrupt/directives.rst:2620::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2621- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-2622- ``server_index``. -- c-user/interrupt/directives.rst:2624::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2625- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-2626- ``vector``. -- c-user/interrupt/directives.rst:2700::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2701- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-2702- ``server_index``. -- c-user/interrupt/directives.rst:2764::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2765- There was no interrupt server associated with the server index specified by c-user/interrupt/directives.rst-2766- ``server_index``. -- c-user/interrupt/directives.rst:2822::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2823- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-2824- ``server_index``. -- c-user/interrupt/directives.rst:2876::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2877- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-2878- ``server_index``. -- c-user/interrupt/directives.rst:2944::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2945- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-2946- ``source_server_index``. -- c-user/interrupt/directives.rst:2948::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2949- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-2950- ``destination_server_index``. -- c-user/interrupt/directives.rst:2952::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-2953- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-2954- ``vector``. -- c-user/interrupt/directives.rst:3022::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-3023- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-3024- ``server_index``. -- c-user/interrupt/directives.rst:3026::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-3027- There was no interrupt vector associated with the number specified by c-user/interrupt/directives.rst-3028- ``vector``. -- c-user/interrupt/directives.rst:3087::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-3088- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-3089- ``server_index``. -- c-user/interrupt/directives.rst:3354::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-3355- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-3356- ``server_index``. -- c-user/interrupt/directives.rst:3438::c:macro:`RTEMS_INVALID_ID` c-user/interrupt/directives.rst-3439- There was no interrupt server associated with the index specified by c-user/interrupt/directives.rst-3440- ``server_index``.
Author: Chris Johns
2024-05-25T08:50:05.113Z
All I am asking is there is a reminder to the user to check the BSP specifics to find out if the feature is supported. With out this a new user or a user that does not know the BSP or RTEMS may assume what they are doing is the reason.
Author: Chris Johns
2024-05-25T08:49:59.854Z
But they can use the attach calls or should they be naked?
Author: Sebastian Huber
2024-05-25T08:49:59.854Z
If this works or not depends on the architecture and chip.
Author: Chris Johns
2024-05-25T08:49:59.854Z
Then I suggest this be explained.
Author: Sebastian Huber
2024-05-24T08:47:15.779Z
changed this line in version 3 of the diff
Author: Chris Johns
2024-05-21T11:36:06.524Z
This is fine but I think the same issue as the code is the state when there is a lack of support. It could be confusing to a new user if the call fails and the BSP is missing the support.
Author: Sebastian Huber
2024-05-21T12:58:50.223Z
I would say that changing the interrupt priorities is something for experts. You have to know the constraints of the interrupt controller to work with them. The BSP documentation should address the implementation status.
Author: Sebastian Huber
2024-05-24T08:47:15.966Z
added 16 commits
a72be6ec…b0e04597 - 15 commits from branch
rtems/docs:mainfda289c6 - c-user: Document get/set interrupt priority
Author: Sebastian Huber
2024-05-25T08:50:17.816Z
I updated the documentation do address the review comments.
Author: Chris Johns
2024-05-25T08:50:17.816Z
Looks good. Can you please rebase and resolve the threads you have addressed with the update. I cannot get a merge button until that happens. Thanks.
Author: Sebastian Huber
2024-05-25T08:50:17.833Z
resolved all threads
Author: Sebastian Huber
2024-05-25T08:50:30.100Z
added 6 commits
fda289c6…e0fe7026 - 5 commits from branch
rtems/docs:main79201f7d - c-user: Document get/set interrupt priority
Author: Sebastian Huber
2024-05-25T08:53:27.287Z
added 1 commit
6810ec1a - c-user: Document get/set interrupt priority
Author: Chris Johns
2024-05-28T21:19:59.350Z
approved this merge request
Author: Chris Johns
2024-05-28T21:20:17.407Z
added 3 commits
6810ec1a…35cae580 - 2 commits from branch
rtems/docs:maind196c8bc - c-user: Document get/set interrupt priority
15 - Fix parallel building¶
Id |
15 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2024-05-27T04:02:10.656Z |
Assignee(s) |
Chris Johns |
Created |
2024-05-26T07:20:08.327Z |
Updated |
2024-05-27T04:02:11.522Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/15 |
Commit |
Summary¶
Fix parallel building. An add group serialised the build
Author: Chris Johns
2024-05-26T07:20:10.583Z
assigned to @chris
Author: Chris Johns
2024-05-26T21:51:48.714Z
added 1 commit
ee26182c - waf: Fix parallel building
Author: Amar Takhar
2024-05-27T04:01:07.377Z
approved this merge request
Author: Amar Takhar
2024-05-27T04:01:17.497Z
added 3 commits
ee26182c…5fe30b37 - 2 commits from branch
rtems/docs:main35cae580 - waf: Fix parallel building
13 - Fix the README file name¶
Id |
13 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2024-05-25T05:01:53.285Z |
Assignee(s) |
Chris Johns |
Reviewer(s) |
Amar Takhar |
Created |
2024-05-25T05:01:13.755Z |
Updated |
2024-05-25T05:01:54.144Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/13 |
Commit |
Summary¶
This fixes the basic mistake in !12
Author: Chris Johns
2024-05-25T05:01:13.877Z
requested review from @amar
Author: Chris Johns
2024-05-25T05:01:13.890Z
assigned to @chris
Author: Amar Takhar
2024-05-25T05:01:49.733Z
approved this merge request
12 - Move README to markdown¶
Id |
12 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2024-05-25T04:57:20.180Z |
Assignee(s) |
Chris Johns |
Created |
2024-05-25T04:49:29.439Z |
Updated |
2024-05-25T05:01:16.182Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/12 |
Commit |
Summary¶
Move the README to markdown and clean up the formatting
Author: Chris Johns
2024-05-25T04:49:29.633Z
assigned to @chris
Author: Chris Johns
2024-05-25T04:53:56.938Z
added 1 commit
39cabd5c - docs: Move README to markdown and clean up
Author: Amar Takhar
2024-05-25T04:57:11.940Z
approved this merge request
Author: Amar Takhar
2024-05-25T04:58:33.848Z
OK .. this is a first for me I can’t believe I missed that.
Author: Amar Takhar
2024-05-25T04:58:41.458Z
Look at the filename…
Author: Chris Johns
2024-05-25T05:01:16.159Z
mentioned in merge request !13
11 - Resolve “Manuals refer to git.rtems.org”¶
Id |
11 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2024-05-18T04:03:52.155Z |
Assignee(s) |
Gedare Bloom |
Reviewer(s) |
Chris Johns |
Created |
2024-05-16T19:12:25.274Z |
Updated |
2024-05-18T04:05:25.899Z |
Milestone |
6.1 |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/11 |
Commit |
Summary¶
Rewrites most of the links to point to gitlab. A few are still remaining that should be cleaned up later.
Closes #10
Author: Gedare Bloom
2024-05-16T19:12:25.396Z
requested review from @chris
Author: Gedare Bloom
2024-05-16T19:12:25.415Z
assigned to @gedare
Author: Gedare Bloom
2024-05-16T19:13:30.061Z
added 12 commits
07c13c07…9134a174 - 4 commits from branch
rtems/docs:main401bec9e - user/start: fix git.rtems.org links
59bbe982 - user/installation/developer: fix links to git.rtems.org
0a79c27b - user/deployment/index.rst: fix links to git.rtems.org
2e25946d - user/bld/index.rst: fix links to git.rtems.org
9d303608 - user/tracing/tracelinker.rst: fix links to git.rtems.org
16f871b2 - eng/release-process.rst: fix links to git.rtems.org
61343276 - filesystem/trivial_ftp.rst: fix link to git.rtems.org
1c7ae3d9 - legacy-networking/quick_start.rst: fix link to git.rtems.org
Author: Gedare Bloom
2024-05-17T14:37:21.309Z
added 8 commits
37144d24 - user/start: fix git.rtems.org links
00a8abee - user/installation/developer: fix links to git.rtems.org
2af863fd - user/deployment/index.rst: fix links to git.rtems.org
3b90b657 - user/bld/index.rst: fix links to git.rtems.org
a6f9e3ea - user/tracing/tracelinker.rst: fix links to git.rtems.org
d627eab2 - eng/release-process.rst: fix links to git.rtems.org
b56b5d46 - filesystem/trivial_ftp.rst: fix link to git.rtems.org
fb68c842 - legacy-networking/quick_start.rst: fix link to git.rtems.org
Author: Gedare Bloom
2024-05-17T14:38:43.410Z
added 1 commit
91a4d7ad - user/glossary: fix link to yaffs2
Author: Amar Takhar
2024-05-18T04:02:37.496Z
added 11 commits
91a4d7ad…335051ef - 2 commits from branch
rtems/docs:mainddff023c - user/start: fix git.rtems.org links
62216d82 - user/installation/developer: fix links to git.rtems.org
14772d08 - user/deployment/index.rst: fix links to git.rtems.org
3a61ecf1 - user/bld/index.rst: fix links to git.rtems.org
179390e3 - user/tracing/tracelinker.rst: fix links to git.rtems.org
86c21d47 - eng/release-process.rst: fix links to git.rtems.org
70516131 - filesystem/trivial_ftp.rst: fix link to git.rtems.org
1f4d3a24 - legacy-networking/quick_start.rst: fix link to git.rtems.org
62ef5d66 - user/glossary: fix link to yaffs2
Author: Amar Takhar
2024-05-18T04:03:43.938Z
approved this merge request
Author: Amar Takhar
2024-05-18T04:04:24.519Z
dammit this went in as a merge commit argh!
Author: Amar Takhar
2024-05-18T04:05:25.882Z
oh, no it didn’t, I was about to get really upset with myself.
10 - Resolve “Document Merge Request Workflow”¶
Id |
10 |
State |
merged |
Merged by |
Amar Takhar |
Merged at |
2024-05-18T04:02:23.243Z |
Assignee(s) |
Gedare Bloom |
Reviewer(s) |
Chris Johns |
Created |
2024-05-16T16:53:32.583Z |
Updated |
2024-05-18T04:02:24.844Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/10 |
Commit |
Summary¶
Closes #8
Author: Gedare Bloom
2024-05-16T16:53:32.706Z
requested review from @chris
Author: Gedare Bloom
2024-05-16T16:53:32.726Z
assigned to @gedare
Author: Amar Takhar
2024-05-18T04:02:17.802Z
approved this merge request
5 - Resolve “Contributing guidance is outdated”¶
Id |
5 |
State |
merged |
Merged by |
Gedare Bloom |
Merged at |
2024-05-02T04:59:46.045Z |
Assignee(s) |
Gedare Bloom |
Reviewer(s) |
Kinsey Moore |
Created |
2024-05-01T15:22:32.949Z |
Updated |
2024-05-02T04:59:48.265Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/5 |
Commit |
Summary¶
Closes #5
Author: Gedare Bloom
2024-05-01T15:22:33.073Z
requested review from @opticron
Author: Gedare Bloom
2024-05-01T15:22:33.120Z
assigned to @gedare
Author: Chris Johns
2024-05-01T22:38:40.872Z
approved this merge request
Author: Amar Takhar
2024-05-01T22:41:28.873Z
Interesting this is still blocked I thought I set it up properly.
Author: Amar Takhar
2024-05-01T22:41:44.780Z
I think I might know what’s going on.
Author: Gedare Bloom
2024-05-02T04:08:17.321Z
mentioned in merge request !6
3 - Resolve “Rewrite bug user story”¶
Id |
3 |
State |
merged |
Merged by |
Gedare Bloom |
Merged at |
2024-04-30T15:09:02.286Z |
Assignee(s) |
Gedare Bloom |
Reviewer(s) |
Kinsey Moore |
Created |
2024-04-29T17:19:02.450Z |
Updated |
2024-04-30T15:09:03.819Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/3 |
Commit |
Summary¶
Closes #4
Author: Gedare Bloom
2024-04-29T17:19:02.573Z
requested review from @opticron
Author: Gedare Bloom
2024-04-29T17:19:02.590Z
assigned to @gedare
Author: Gedare Bloom
2024-04-29T17:36:15.978Z
added 1 commit
246c735b - user/support/bugs: rewrite bug user story toward gitlab
Author: Gedare Bloom
2024-04-29T17:36:24.571Z
marked this merge request as ready
Author: Amar Takhar
2024-04-29T20:11:12.670Z
approved this merge request
Author: Kinsey Moore
2024-04-30T14:23:25.434Z
added 3 commits
246c735b…e327f319 - 2 commits from branch
mainc2404ead - user/support/bugs: rewrite bug user story toward gitlab
1 - Resolve “Rewrite trac links to gitlab”¶
Id |
1 |
State |
merged |
Merged by |
Gedare Bloom |
Merged at |
2024-04-29T20:14:47.265Z |
Assignee(s) |
Gedare Bloom |
Created |
2024-04-29T14:59:25.659Z |
Updated |
2024-04-29T20:14:48.134Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/1 |
Commit |
Summary¶
Closes #2
Author: Gedare Bloom
2024-04-29T14:59:25.843Z
assigned to @gedare
Author: Gedare Bloom
2024-04-29T15:21:27.666Z
added 2 commits
3dcc9f20 - user/zynqmp-rpu: Add load and debug information
5e0a4381 - common: rewrite trac links to gitlab
Author: Gedare Bloom
2024-04-29T15:21:49.244Z
marked this merge request as ready
Author: Amar Takhar
2024-04-29T20:14:37.024Z
I’m guessing this is not supposed to be part of this merge request?
Author: Gedare Bloom
2024-04-29T20:14:16.061Z
changed this file in version 2 of the diff
Author: Gedare Bloom
2024-04-29T20:14:16.301Z
added 2 commits
6a0e16b9 - 1 commit from branch
maine327f319 - common: rewrite trac links to gitlab
Author: Gedare Bloom
2024-04-29T20:14:37.042Z
resolved all threads
2 - Resolve “sync git.rtems.org”¶
Id |
2 |
State |
merged |
Merged by |
Gedare Bloom |
Merged at |
2024-04-29T20:13:42.255Z |
Assignee(s) |
Gedare Bloom |
Reviewer(s) |
Kinsey Moore |
Created |
2024-04-29T15:09:24.503Z |
Updated |
2024-04-29T20:13:43.384Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/2 |
Commit |
Summary¶
Closes #3
Author: Gedare Bloom
2024-04-29T15:09:24.630Z
requested review from @opticron
Author: Gedare Bloom
2024-04-29T15:09:24.652Z
assigned to @gedare
Author: Gedare Bloom
2024-04-29T15:15:12.556Z
added 1 commit
6a0e16b9 - user/zynqmp-rpu: Add load and debug information
Author: Gedare Bloom
2024-04-29T15:15:20.516Z
marked this merge request as ready
Author: Amar Takhar
2024-04-29T20:10:48.911Z
approved this merge request
7 - CODEOWNERS: mark general approvers as optional and add maintainer approvers (closed)¶
Id |
7 |
State |
closed |
Assignee(s) |
Amar Takhar |
Closed by |
Gedare Bloom |
Created |
2024-05-02T04:51:00.535Z |
Closed |
2024-05-02T05:08:06.500Z |
Updated |
2024-05-02T05:08:06.479Z |
Milestone |
6.1 |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/7 |
Commit |
Summary¶
If this pattern works, we can use it on other repos (other than rtems.git)
Closes #6
Author: Gedare Bloom
2024-05-02T04:51:00.681Z
assigned to @amar
Author: Gedare Bloom
2024-05-02T05:08:06.016Z
the CODEOWNERS file is not modified through an MR
6 - Draft: Resolve “Merge Request Approval process is broken” (closed)¶
Id |
6 |
State |
closed |
Assignee(s) |
Amar Takhar |
Closed by |
Gedare Bloom |
Created |
2024-05-02T04:07:33.161Z |
Closed |
2024-05-02T04:49:03.064Z |
Updated |
2024-05-02T04:49:03.051Z |
Milestone |
6.1 |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/6 |
Commit |
Summary¶
Closes #6
Author: Gedare Bloom
2024-05-02T04:07:33.299Z
assigned to @amar
Author: Gedare Bloom
2024-05-02T04:08:16.735Z
If this looks good, I would like to test the logic out here and see if it frees up the blocked !5
If this pattern works, we can adopt it to the other repos (other than RTEMS.git).
4 - Resolve “Contributing guidance is outdated” (closed)¶
Id |
4 |
State |
closed |
Assignee(s) |
Gedare Bloom |
Reviewer(s) |
Kinsey Moore |
Closed by |
Gedare Bloom |
Created |
2024-04-29T17:47:02.875Z |
Closed |
2024-05-01T14:41:47.430Z |
Updated |
2024-05-01T14:41:47.416Z |
Milestone |
6.1 |
Labels |
doc |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/4 |
Commit |
Summary¶
Closes #5
Author: Gedare Bloom
2024-04-29T17:47:03.007Z
requested review from @opticron
Author: Gedare Bloom
2024-04-29T17:47:03.299Z
assigned to @gedare
Author: Gedare Bloom
2024-04-29T20:03:59.462Z
added 3 commits
dae2f951 - user: update installation section
855c6b36 - user: update contributing guidance in Support section
62d20bc9 - user: update merge approval description
Author: Gedare Bloom
2024-04-29T20:04:19.619Z
marked this merge request as ready
Author: Amar Takhar
2024-04-29T20:11:40.436Z
approved this merge request
Author: Kinsey Moore
2024-04-30T14:23:35.407Z
added 5 commits
62d20bc9…e327f319 - 2 commits from branch
mainb1237168 - user: update installation section
65157c46 - user: update contributing guidance in Support section
6b21418f - user: update merge approval description
Author: Gedare Bloom
2024-04-30T15:10:00.882Z
added 4 commits
c2404ead - 1 commit from branch
mainb773c0af - user: update installation section
d25958d4 - user: update contributing guidance in Support section
6cbff66b - user: update merge approval description
Author: Gedare Bloom
2024-04-30T15:11:36.326Z
This needs to be updated to reflect using forks and not direct MR from an Issue. Also may write documentation how to undo such a direct MR from an Issue and use this MR as a test case for the same.
30 - Draft: Simplify system termination procedure (opened)¶
Id |
30 |
State |
opened |
Assignee(s) |
Sebastian Huber |
Created |
2024-07-17T17:05:33.307Z |
Updated |
2024-07-26T11:07:23.228Z |
Milestone |
6.1 |
Labels |
rtems::testing |
Link |
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/30 |
Commit |
Summary¶
In the system termination procedure, everything after invoking the fatal extensions is essentially dead code. Simplify the procedure and provide a reasonable safe fall-back for badly configured applications. Just disable masked interrupts and execute an idle loop.
This removes the need for CPU ports to provide a fatal halt handler.
Update https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5067
Author: Sebastian Huber
2024-07-17T17:05:33.404Z
assigned to @sebhub
Author: Sebastian Huber
2024-07-17T17:06:52.757Z
marked this merge request as draft
Author: Sebastian Huber
2024-07-18T08:59:16.070Z
marked this merge request as ready
Author: Sebastian Huber
2024-07-18T08:59:16.092Z
changed the description
Author: Amar Takhar
2024-07-23T02:31:25.303Z
changed the description
Author: Kinsey Moore
2024-07-25T22:16:06.069Z
added 5 commits
9df51f3a…f1cd233f - 4 commits from branch
rtems/docs:main46f4ca5b - Simplify system termination procedure
Author: Kinsey Moore
2024-07-25T22:19:46.751Z
“were” -> “are”
Author: Sebastian Huber
2024-07-26T11:06:44.954Z
Actually, right now in the code, the fatal extensions are invoked without explicitly disabling maskable interrupts. After a second look, I think this should be changed as well to:
void _Terminate( Internal_errors_Source the_source, Internal_errors_t the_error ) { ISR_Level level; _ISR_Local_disable( level ); (void) level; _User_extensions_Fatal( the_source, the_error ); /* * Everything after invoking the fatal extensions is essentially dead code. * At least one fatal extension of the initial extension sets should not * return and for example reset the system. See section "System Termination * Procedure" in the RTEMS Classic API Guide. * * The following code is only executed in badly configured applications. */ _CPU_Thread_Idle_body( 0 ); }
Author: Kinsey Moore
2024-07-25T22:19:47.201Z
requested changes
Author: Sebastian Huber
2024-07-26T11:07:23.309Z
marked this merge request as draft