Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-11 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113089


My comment was wrong and meant to say I decided not to change the VC related 
bits other than remove the default. I will review it when I can.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113089
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-11 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113087


Thanks for the feedback. I ran yapf and it had changes which surprised me. I 
will update the MR. The git bit is specific where the format allows any label. 
I decided to change that in the code.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113087
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-11 Thread Chris Johns (@chris)



Chris Johns commented on a discussion on wscript: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113085

 >  #define _RTEMS_VERSION_VC_KEY_H_
 >  """
 >  key = bld.env.RTEMS_VERSION_CONTROL_KEY
 > -if key == "git":

Ah no, thanks. I take a look when I can.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113085
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-11 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113083


I am sorry you think that. I have done nothing more than be consistent with the 
release format used.

I took the time a long time ago to design the format and make all parts of the 
eco-system consistent.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113083
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-10 Thread Chris Johns (@chris)



Chris Johns commented on a discussion on wscript: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113080

 >  
 >  
 >  def options(ctx):
 > +load_version()

The help displays the path

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113080
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-10 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113079


Your version is your version. You comment no one else should care while at the 
same time you do care so I kind of feel you are answering your questions. The 
format I made a long time ago should persist. I am sorry this causes you 
problems but I have done my best to make it standard and  maintain that.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113079
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-10 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113075


The ticket has existed for a while so it was always going to be made 
consistent. I have no intention of changing all the other places.

The release scripts update was for gitlab not this.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113075
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-10 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113073


The VERSION file is more complex than just your values. The format has been 
documented for a while 
https://gitlab.rtems.org/rtems/tools/rtems-tools/-/blob/main/rtemstoolkit/version.py?ref_type=heads#L32

Why do you care?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113073
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-10 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113071


I have no idea why you decided to change it and break the release process. I 
have fixed it.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257#note_113071
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-10 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257

Project:Branches: chris/rtems:5037-waf-does-not-handle-version-file to 
rtems/rtos/rtems:main
Author:   Chris Johns
Assignee: Chris Johns



Fix handling of the `VERSION` file in a release. The change output with the 
6.1-rc4 `VERSION` file is:

```
*** BEGIN OF TEST HELLO WORLD ***
*** TEST VERSION: 6.1.0.rc4
*** TEST STATE: EXPECTED_PASS
*** TEST BUILD: RTEMS_DEBUG RTEMS_POSIX_API
*** TEST TOOLS: 13.3.0 20240521 (RTEMS 6, RSB 
b95871822032635b2ccbee23b97a19e66d2b003e-modified, Newlib 1b3dcfd)
Hello World

*** END OF TEST HELLO WORLD ***


[ RTEMS shutdown ]
RTEMS version: 6.1.0.rc4
RTEMS tools: 13.3.0 20240521 (RTEMS 6, RSB 
b95871822032635b2ccbee23b97a19e66d2b003e-modified, Newlib 1b3dcfd)
executing thread ID: 0x0a010001
executing thread name: UI1
```

Fixes #5037



Closes #5037

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Fix handling of the VERSION file in a release (!257)

2024-10-10 Thread Chris Johns (@chris)


Reassigned merge request 257

https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/257
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Source Builder | Re-evaluate mirrors on our GitHub (#16)

2024-10-10 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/16#note_113060


The only place this is an issue is the git repos so do we need to deal with 
this for release branches? All releases building with the RSB pull from 
ftp.rtems.org.

I do not see us bisect'nig the RSB repo which would be an issue.

If we agree this is the case can we update the configs in 4 and 5 and make new 
dot releases?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/16#note_113060
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Release | Update with RTEMS 6 and Gitlab changes (!10)

2024-10-10 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/10

Project:Branches: chris/rtems-release:r-6-updates to 
rtems/rtos/rtems-release:main
Author:   Chris Johns
Assignee: Chris Johns



Update the release scripts to build a release from Gitlab.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/10
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Release | Update with RTEMS 6 and Gitlab changes (!10)

2024-10-10 Thread Chris Johns (@chris)


Reassigned merge request 10

https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/10

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/10
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Source Builder | dtc: do not attempt to build on windows (!66)

2024-10-10 Thread Chris Johns (@chris)



Chris Johns started a new discussion on source-builder/config/dtc-1-1.cfg: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/66#note_113047

 >  # This configuration file configure's, make's and install's DTC.
 >  #
 >  
 > +%ifos win32 mingw mingw32
 > +%warning DTC does not build on this host, skipping.
 > +%else
 > +

This should be indented but I get why you have not.

Would it be nicer and simpler to have the RSB **_finish_** the config 
processing?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/66#note_113047
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Tools | Fix windows build with MSYS2 (!30)

2024-10-09 Thread Chris Johns (@chris)


Merge request !30 was merged
Merge request URL: 
https://gitlab.rtems.org/rtems/tools/rtems-tools/-/merge_requests/30
Project:Branches: gedare/rtems-tools:fix_windows to rtems/tools/rtems-tools:main
Author: Gedare Bloom

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-tools/-/merge_requests/30
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Source Builder | sb:sources: Do not raise an error adding a hash if one is present (!65)

2024-10-09 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/65

Project:Branches: 
chris/rtems-source-builder:40-adding-a-hash-in-a-release-build-generates-an-error
 to rtems/tools/rtems-source-builder:main
Author:   Chris Johns
Assignee: Chris Johns



Do not raise an error adding a hash if one is present

Fixes #40



Closes #40

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/65
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Source Builder | sb:sources: Do not raise an error adding a hash if one is present (!65)

2024-10-09 Thread Chris Johns (@chris)


Reassigned merge request 65

https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/65

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/65
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Tools | Update waf (!29)

2024-10-09 Thread Chris Johns (@chris)


Merge request !29 was merged
Merge request URL: 
https://gitlab.rtems.org/rtems/tools/rtems-tools/-/merge_requests/29
Project:Branches: gedare/rtems-tools:update_waf to rtems/tools/rtems-tools:main
Author: Gedare Bloom

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-tools/-/merge_requests/29
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Source Builder | Adding a hash in a release build generates an error (#40)

2024-10-09 Thread Chris Johns (@chris)


Chris Johns created an issue: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/40

Assignee: Chris Johns

Releases provide the release tar file hash in the `VERSION` file. This is read 
and loaded when the RSB starts a set build. If the package being built has a 
development hash in its configuration file the addition of that hash to the 
hash table results in an error because the hash is present and the value is 
different.

If the RSB is in release mode (`%{release} == 1`) do not raise an error. This 
lets the error happen during development if there is a duplicate and lets us 
ship untouched config files with the release versions of the tar files and 
hashes defined in `VERSION`.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/40
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Release | rtems-notes-6.1.md: Add missing BSPs to added and removed lists (!8)

2024-10-09 Thread Chris Johns (@chris)


Merge request !8 was merged
Merge request URL: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/8
Project:Branches: joel/rtems-release:update-new-bsps to 
rtems/rtos/rtems-release:main
Author: Joel Sherrill
Assignee: Joel Sherrill
Reviewer: Chris Johns

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/8
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Release | rtems-notes-6.1.md: Add missing BSPs to added and removed lists (!8)

2024-10-09 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/8#note_113023


Awesome and thanks

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/8#note_113023
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Documentation | Finding a place for LibBSD and other Package Documentation (#35)

2024-10-09 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/issues/35#note_113022


@joel would you like to please comment about the Legacy documentation?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/issues/35#note_113022
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Release | rtems-notes-6.1.md: Added 14 m68k BSPs for Deprecation (!7)

2024-10-08 Thread Chris Johns (@chris)


Merge request !7 was merged
Merge request URL: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/7
Project:Branches: joel/rtems-release:deprecate-m68k-bsps to 
rtems/rtos/rtems-release:main
Author: Joel Sherrill
Assignee: Joel Sherrill
Reviewer: Chris Johns

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/7
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Deprecate bfin port in rtems6 (#5019)

2024-10-08 Thread Chris Johns (@chris)


Issue was closed by Chris Johns with merge request !6 
(https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/6)
Issue #5019: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5019

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5019
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Deprecate lm32 port in rtems6 (#5020)

2024-10-08 Thread Chris Johns (@chris)


Issue was closed by Chris Johns with merge request !6 
(https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/6)
Issue #5020: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5020

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5020
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Deprecate Multiple m68k BSPs in rtems6 (#5030)

2024-10-08 Thread Chris Johns (@chris)


Issue was closed by Chris Johns with merge request !6 
(https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/6)
Issue #5030: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5030

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5030
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Release | Update Deprecation of BSPs and Architectures (!6)

2024-10-08 Thread Chris Johns (@chris)


Merge request !6 was merged
Merge request URL: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/6
Project:Branches: joel/rtems-release:deprecate-more-bsps-and-architectures to 
rtems/rtos/rtems-release:main
Author: Joel Sherrill
Assignee: Joel Sherrill
Reviewer: Gedare Bloom

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/6
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Deprecate Multiple m68k BSPs in rtems6 (#5030)

2024-10-08 Thread Chris Johns (@chris)


Reassigned Issue 5030

https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5030

Joel Sherrill was added as an assignee.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5030
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Deprecate lm32 port in rtems6 (#5020)

2024-10-08 Thread Chris Johns (@chris)


Reassigned Issue 5020

https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5020

Joel Sherrill was added as an assignee.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5020
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Deprecate bfin port in rtems6 (#5019)

2024-10-08 Thread Chris Johns (@chris)


Reassigned Issue 5019

https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5019

Joel Sherrill was added as an assignee.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5019
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Documentation | Finding a place for LibBSD and other Package Documentation (#35)

2024-10-08 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/issues/35#note_112979


A split as discussed sounds good to me. A top level section called "Packages" 
would be easy to see and most users should understand what is meant by packages.

The RSB has packages as well. Would they be listed as well some how?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/issues/35#note_112979
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Source Builder | User manual RSB BSP build examples need updating (#39)

2024-10-07 Thread Chris Johns (@chris)


Chris Johns created an issue: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/39

Assignee: Chris Johns



-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/39
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Source Builder | Windows only code in common area in path.py (#38)

2024-10-07 Thread Chris Johns (@chris)


Issue was closed by Chris Johns with merge request !64 
(https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/64)
Issue #38: https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/38

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/38
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Source Builder | sys.getwindowsversion only exists on Windows. (!64)

2024-10-07 Thread Chris Johns (@chris)


Merge request !64 was merged
Merge request URL: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/64
Project:Branches: amar/rtems-source-builder:fix to 
rtems/tools/rtems-source-builder:main
Author: Amar Takhar
Assignee: Amar Takhar

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/64
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Source Builder | Windows only code in common area is path.py (#38)

2024-10-07 Thread Chris Johns (@chris)


Chris Johns created an issue: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/38

Assignee: Gedare Bloom

The change to detect Windows 11 in !63 is in the common area and should have 
been guarded with a check of `nt`. It has broken non-Windows builds:

```
windows11 = sys.getwindowsversion().build >= 22000
^
AttributeError: module 'sys' has no attribute 'getwindowsversion'
```

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/38
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Documentation | user: Document ZynqMP RPU BSP variants (!52)

2024-10-06 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/52#note_112927


Looks good. Would it be possible to include a small paragraph about the memory 
map and how the users create a suitable hole in the APU address map to 
accommodate the R5 cores?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/52#note_112927
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS | README.md does not reference the main branch (#5133)

2024-10-05 Thread Chris Johns (@chris)


Chris Johns created an issue: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5133

Assignee: Joel Sherrill

The README test has `master` are now using `main`. The URLs need to be reviewed 
and updated.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5133
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Release | Minor updates (!5)

2024-10-05 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/5

Project:Branches: chris/rtems-release:minor-updates to 
rtems/rtos/rtems-release:main
Author:   Chris Johns
Assignee: Chris Johns



Only build the PDF release note is `pdflatex` is found.

Update the `pip` dependencies needed.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/5
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Release | Minor updates (!5)

2024-10-05 Thread Chris Johns (@chris)


Reassigned merge request 5

https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/5

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/5
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Legacy Networking | Waf fixes 2.1.2 (!4)

2024-10-04 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy/-/merge_requests/4

Project:Branches: chris/rtems-net-legacy:waf-fixes-2.1.2 to 
rtems/pkg/rtems-net-legacy:main
Author:   Chris Johns
Assignee: Chris Johns



Update to waf 2.1.2 and pick up the latest `rtems_waf`



-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy/-/merge_requests/4
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Legacy Networking | Waf fixes 2.1.2 (!4)

2024-10-04 Thread Chris Johns (@chris)


Reassigned merge request 4

https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy/-/merge_requests/4

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/pkg/rtems-net-legacy/-/merge_requests/4
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Network Services | Update waf to 2.1.2 (!6)

2024-10-04 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/pkg/rtems-net-services/-/merge_requests/6

Project:Branches: chris/rtems-net-services:update-waf-to-2.1.2 to 
rtems/pkg/rtems-net-services:main
Author:   Chris Johns
Assignee: Chris Johns



Update to the latest waf. This also resulted in:

1. Updating `rtems_waf`
2. Fixing some bugs in the net services help



-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/pkg/rtems-net-services/-/merge_requests/6
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Network Services | Update waf to 2.1.2 (!6)

2024-10-04 Thread Chris Johns (@chris)


Reassigned merge request 6

https://gitlab.rtems.org/rtems/pkg/rtems-net-services/-/merge_requests/6

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/pkg/rtems-net-services/-/merge_requests/6
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Documentation | Say to install MSYS2 installer and update pic (#34)

2024-10-04 Thread Chris Johns (@chris)


Chris Johns created an issue: 
https://gitlab.rtems.org/rtems/docs/rtems-docs/-/issues/34

Assignee: Gedare Bloom

## Summary

It has been pointed out to me the Windows documentation does not actually say 
to install the installer. Best to be clear about this.

Also the pic needs to be updated,

## Steps to reproduce

Read the documentation.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/issues/34
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Waf | python: Fix escapes reported by python 3.12 (!8)

2024-10-03 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/tools/rtems_waf/-/merge_requests/8

Project:Branches: chris/rtems_waf:fix-py-3.12-escapes to 
rtems/tools/rtems_waf:main
Author:   Chris Johns
Assignee: Chris Johns



This cleans up the escapes reported by python 3.12

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems_waf/-/merge_requests/8
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Waf | python: Fix escapes reported by python 3.12 (!8)

2024-10-03 Thread Chris Johns (@chris)


Reassigned merge request 8

https://gitlab.rtems.org/rtems/tools/rtems_waf/-/merge_requests/8

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems_waf/-/merge_requests/8
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS | waf: Update waf to version 2.1.2 (!250)

2024-10-03 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/250

Project:Branches: chris/rtems:update-waf-to-2.1.2 to rtems/rtos/rtems:main
Author:   Chris Johns
Assignee: Chris Johns



Update waf to version 2.1.2

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/250
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | waf: Update waf to version 2.1.2 (!250)

2024-10-03 Thread Chris Johns (@chris)


Reassigned merge request 250

https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/250

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/250
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS | git: Remove auto* files from git ignore (!249)

2024-10-03 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/249

Project:Branches: chris/rtems:cleanup-git-ignore to rtems/rtos/rtems:main
Author:   Chris Johns
Assignee: Chris Johns



Remove the autotool generated files.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/249
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | git: Remove auto* files from git ignore (!249)

2024-10-03 Thread Chris Johns (@chris)


Reassigned merge request 249

https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/249

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/249
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-10-01 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112762


Thanks. I am OK with this.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112762
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-10-01 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112759


Thanks for the update. 

Just so I understand the change, a user wanting to have the APU and two RPUs 
would build the APU with a suitable memory map and then the `split_0` and 
`split_1` BSPs only updating the memory map options?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112759
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Source Builder | x86_64 breaks on MacOS M machines (#35)

2024-10-01 Thread Chris Johns (@chris)


Chris Johns created an issue: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/35

Assignee: Joel Sherrill

Building the `x86_64` tools on MacOS M silicon fails with:

```
config: tools/rtems-grub-2.06.cfg
grub2.cfg:11: "Darwin does not support Grub2 compilation by default."
grub2.cfg:12: "If you need Grub2 on Darwin, please install objconv"
grub2.cfg:13: "and enable it by removing '%undefine grub2_platform_supported' 
above"
config: tools/rtems-makefs-r12.cfg
package: makefs-v12-arm64-apple-darwin23.6.0-1
download: https://codeload.github.com/kusumi/makefs/tar.gz/r12 -> 
sources/makefs-r12.tar.gz
downloading: sources/makefs-r12.tar.gz - 646.2kB
building: makefs-v12-arm64-apple-darwin23.6.0-1
error: building makefs-v12-arm64-apple-darwin23.6.0-1
Build FAILED
  See error report: rsb-report-makefs-v12-arm64-apple-darwin23.6.0-1.txt
  Note: In some cases the error appears only in
  the complete build log (see --log option)
error: building makefs-v12-arm64-apple-darwin23.6.0-1
```

Why is grub being built?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/35
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-30 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112751


Thanks for testing details. Lets wait to hear from @opticron

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112751
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-30 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112749


We have so many options we do not map to specific BSPs. I am fine with the two 
BSPs names I provided. I would also like to hear from @opticron about the 
differences with split mode.

in regards to testing, we have no means to test two BSPs in hardware at once. 
How do you do that?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112749
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-30 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112747


A user will need to consider a memory map that works and that will be 
determined by their system design. An example (with make up bits and pieces) is:

```
[aarch64/zynqmp_apu]
BASE = 0x000a

[aarch64/zynqmp_rpu_0]
INHERIT = aarch64/zynqmp_rpu
BASE = 0x0001
SIZE = 0x0004
ZYQMP_RPU_INT_CONTROLLER_MODE = shared,primary

[aarch64/zynqmp_rpu_1]
INHERIT = aarch64/zynqmp_rpu
BASE = 0x0005
SIZE = 0x0004
ZYQMP_RPU_INT_CONTROLLER_MODE = shared,secondary
```

The user can build the suite of BSPs needed from the base ones we provide.

I have no idea if adjusting the base address of the APU like this works, it is 
just an example. It might be the RPU memory descend down from the top of the 
below 2G area.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112747
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-30 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112745


Would:

1. `zynqmp_rpu`
2. `zynqmp_rpu_lock_step`

work?

The coverage etc is a good point, thanks.

Who says the options you select are right? Why is the memory size you have 
selected correct for everyone?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112745
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-30 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112743


In regards to "the details are in the patch", I did not see this detail. This 
conversation makes it easier for others to see what is happening and how things 
are designed. I do not assuming everyone sees what you or I do.

Can the RPU determine if it is in lock step mode or which core it is?

I suggest a single BSP name `zynqmp_rpu` with defaults for a single address 
space block and basic initialization that can run the tests. INI options can 
then change the address map and the initialization as required.

A BSP name will go only so far before it does not help. There are too many 
combinations to expand into BSP names to be practical, for example 
`zynqmp_rpu_split_0_apu` etc. You would also need `zynqmp_apu_rpu_0` and 
`zynqmp_apu_rpu_0_1` etc if you wish to run all the APU codes with both RPU 
cores.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112743
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-30 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112741


Is this to provide a separate base address for each build of the BSP?

What is the interrupt controller differences?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112741
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-30 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112739


I understand the types, I do not understand why we need to define BSPs. Is the 
ABI different?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112739
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-30 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112736


Could you please explain why there are qualifiers such as `_lock_step` and 
`_split_0` etc?

I am not in favor of `r5_*` for the same reason I do not think `a53` should be 
present. Those names are SoC implementation details and the documentation block 
diagrams from the manufacture refer to RPU and APU.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112736
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Source Builder | www/civetweb: Add thread configuration parameters (#34)

2024-09-30 Thread Chris Johns (@chris)


Chris Johns created an issue: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/34

Assignee: Chris Johns

## Summary

The Mongoose web server in RTEMS supports:

1. `thread_stack_size`
2. `thread_priority` 
3. `thread_policy`

These values lets you control the thread workers. At the moment these values 
are hard coded in the build and the POSIX thread defaults.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/issues/34
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Deployment | amd: Add civetweb package to the package stack (!10)

2024-09-29 Thread Chris Johns (@chris)


Merge request !10 was merged
Merge request URL: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/10
Project:Branches: chris/rtems-deployment:amd-add-civetweb to 
rtems/tools/rtems-deployment:main
Author: Chris Johns
Assignee: Chris Johns

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/10
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Deployment | amd: Add civetweb package to the package stack (!10)

2024-09-29 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/10

Project:Branches: chris/rtems-deployment:amd-add-civetweb to 
rtems/tools/rtems-deployment:main
Author:   Chris Johns
Assignee: Chris Johns



Add the `civetweb` package to the AMD BSP's software stack.



-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/10
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Deployment | amd: Add civetweb package to the package stack (!10)

2024-09-29 Thread Chris Johns (@chris)


Reassigned merge request 10

https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/10

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/10
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Source Builder | rtems/www: Add civetweb web server package (!60)

2024-09-29 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/60

Project:Branches: chris/rtems-source-builder:civetweb to 
rtems/tools/rtems-source-builder:main
Author:   Chris Johns
Assignee: Chris Johns



Add support to build `civetweb` as a package.

Note: 

1. The thread type and thread stack size is currently hard coded and not part 
of the configuration. 
2. I have created Github PR [rtems: Add support for 
RTEMS](https://github.com/civetweb/civetweb/pull/1301) for the patch in my repo.
3. Only tested with libbsd.



-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/60
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Source Builder | rtems/www: Add civetweb web server package (!60)

2024-09-29 Thread Chris Johns (@chris)


Reassigned merge request 60

https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/60

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/60
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-29 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112710


Do need to identify the RPU when split? Could that be a `bootgen` or runtime 
loading choice?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112710
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve arm/xilinx-zynqmp-rpu BSP familiy (!230)

2024-09-29 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112709


Should the RPU then be labeled `r5whatever`? I like `rpu` so maybe the `a53` 
should be removed or change to be `apu` so it aligns with the Xilinx 
documentation?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/230#note_112709
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Improve and simplify SMP start (!235)

2024-09-29 Thread Chris Johns (@chris)


Merge request https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/235 
was reviewed by Chris Johns

--
  
Chris Johns started a new discussion on 
bsps/arm/altera-cyclone-v/start/bspsmp.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/235#note_112700

 >  {
 > -  bool started;
 > +  _Assert(cpu_index == 1);

Why only start cpu 1?

--
  
Chris Johns started a new discussion on cpukit/include/rtems/score/smpimpl.h: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/235#note_112701

 > + * The waiting is done without a timeout.  If secondary processors cannot 
 > reach
 > + * this state, then it is expected that they indicate this failure with an
 > + * ::SMP_MESSAGE_SHUTDOWN message or reset the system.

Is this what happens or is it something that should be done?


-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/235
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Draft: cpukit/libdl/arm: Support BLX relocations that require a trampoline (!244)

2024-09-27 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/244#note_112650


Does this still need to be draft?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/244#note_112650
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Deployment | amd: Add yaml-cpp package to the package stack (!9)

2024-09-26 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/9

Project:Branches: chris/rtems-deployment:amd-add-yaml-cpp to 
rtems/tools/rtems-deployment:main
Author:   Chris Johns
Assignee: Chris Johns



Add `yaml-cpp` as a patch to the vertical stack to the AMD BSPs.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/9
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Deployment | amd: Add yaml-cpp package to the package stack (!9)

2024-09-26 Thread Chris Johns (@chris)


Reassigned merge request 9

https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/9

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/9
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Source Builder | rtems/devel: Add yaml-cpp package (!59)

2024-09-26 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/59

Project:Branches: chris/rtems-source-builder:yaml-cpp to 
rtems/tools/rtems-source-builder:main
Author:   Chris Johns
Assignee: Chris Johns



Add `yaml-cpp` as a package.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/59
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Source Builder | rtems/devel: Add yaml-cpp package (!59)

2024-09-26 Thread Chris Johns (@chris)


Reassigned merge request 59

https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/59

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-source-builder/-/merge_requests/59
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: LibBSD | Add FreeBSD 14 support (#6)

2024-09-25 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/issues/6#note_112598


The directory `ipsec-tools` will not be brought into the `6-freebsd14` branch. 
The [project shutdown in 2014](https://ipsec-tools.sourceforge.net/).

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/issues/6#note_112598
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | cpukit/libdl/arm: Add support for Thumb to ARM transitions and accompanying test (!223)

2024-09-24 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/223#note_112539


Yes but the test is built for all ARM BSPs so lets check.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/223#note_112539
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | cpukit/libdl/arm: Add support for Thumb to ARM transitions and accompanying test (!223)

2024-09-24 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/223#note_112537


Did you build the BBB? It is am ARM only build, no thumb? I use it to check any 
ARM/thumb related changes.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/223#note_112537
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: LibBSD | Kernel RPC header installed (#9)

2024-09-24 Thread Chris Johns (@chris)


Issue was closed by Chris Johns
Issue #9: https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/issues/9

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/issues/9
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | cpukit/libdl/arm: Add support for Thumb to ARM transitions and accompanying test (!223)

2024-09-24 Thread Chris Johns (@chris)



Chris Johns started a new discussion on cpukit/libdl/rtl-mdreloc-arm.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/223#note_112529

 >if (!parsing) {
 > +uint16_t bl_tmp;
 > +
 >  sign = (tmp >> 24) & 1;
 >  *(uint16_t *)where = (uint16_t)((upper_insn & 0xf800) | (sign << 
 > 10) |
 >  ((tmp >> 12) & 0x3ff));
 >  
 > -*((uint16_t *)where + 1) = (uint16_t)((lower_insn & 0xd000)|
 > -  ((sign ^ (~(tmp >> 23) & 1)) 
 > << 13) |
 > -  ((sign ^ (~(tmp >> 22) & 1)) 
 > << 11) |
 > -  ((tmp >> 1) & 0x7ff));
 > +bl_tmp = (uint16_t)((lower_insn & 0xd000)|
 > +   ((sign ^ (~(tmp >> 23) & 1)) << 13) |
 > +   ((sign ^ (~(tmp >> 22) & 1)) << 11) |
 > +   ((tmp >> 1) & 0x7ff));
 > +/* Thumb jumps to ARM mode must have 0 in the LSB of the BLX */

Legft aligned white space?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/223#note_112529
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Reformat cpukit rtems src (!237)

2024-09-23 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112489


I second this, it is great work and the results look great.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112489
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Reformat cpukit rtems src (!237)

2024-09-23 Thread Chris Johns (@chris)



Chris Johns started a new discussion on cpukit/rtems/src/timerserver.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112488

 >  while ( true ) {
 > -  Watchdog_Control  *the_watchdog;
 > -  Timer_Control *the_timer;
 > -  rtems_timer_service_routine_entry  routine;
 > -  Objects_Id id;
 > -  void  *user_data;
 > -
 > -  the_watchdog = (Watchdog_Control *) _Chain_Get_unprotected( 
 > &ts->Pending );
 > +  Watchdog_Control *the_watchdog;
 > +  Timer_Control*the_timer;
 > +  rtems_timer_service_routine_entry routine;
 > +  Objects_Idid;
 > +  void *user_data;
 > +
 > +  the_watchdog = (Watchdog_Control *) _Chain_Get_unprotected( 
 > &ts->Pending
 > +  );

This split is a bit rough. Only a tool could ever do this which means all 
changes need the tool to be merged.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112488
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Reformat cpukit rtems src (!237)

2024-09-23 Thread Chris Johns (@chris)



Chris Johns started a new discussion on cpukit/rtems/src/clockgettod.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112483

 > -#define RTEMS_SECS_PER_HOUR   (RTEMS_SECS_PER_MINUTE * 
 > RTEMS_MINUTE_PER_HOUR)
 > -#define RTEMS_HOURS_PER_DAY   (24UL)
 > -#define RTEMS_SECS_PER_DAY(RTEMS_SECS_PER_HOUR * RTEMS_HOURS_PER_DAY)
 > -#define RTEMS_DAYS_PER_YEAR   (365UL)
 > -#define RTEMS_YEAR_BASE   (1970UL)
 > -
 > -static bool _Leap_year(
 > -  uint32_t year
 > -)
 > +#define RTEMS_SECS_PER_MINUTE ( 60UL )
 > +#define RTEMS_MINUTE_PER_HOUR ( 60UL )
 > +#define RTEMS_SECS_PER_HOUR ( RTEMS_SECS_PER_MINUTE * RTEMS_MINUTE_PER_HOUR 
 > )
 > +#define RTEMS_HOURS_PER_DAY ( 24UL )
 > +#define RTEMS_SECS_PER_DAY ( RTEMS_SECS_PER_HOUR * RTEMS_HOURS_PER_DAY )
 > +#define RTEMS_DAYS_PER_YEAR ( 365UL )
 > +#define RTEMS_YEAR_BASE ( 1970UL )

The  alignment on the macros help view and check but not a big issue.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112483
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Reformat cpukit rtems src (!237)

2024-09-23 Thread Chris Johns (@chris)



Chris Johns started a new discussion on cpukit/rtems/src/statustext.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112487

 > -  "RTEMS_PROXY_BLOCKING"
 > +  "RTEMS_SUCCESSFUL","RTEMS_TASK_EXITTED",
 > +  "RTEMS_MP_NOT_CONFIGURED", "RTEMS_INVALID_NAME",
 > +  "RTEMS_INVALID_ID","RTEMS_TOO_MANY",
 > +  "RTEMS_TIMEOUT",   "RTEMS_OBJECT_WAS_DELETED",
 > +  "RTEMS_INVALID_SIZE",  "RTEMS_INVALID_ADDRESS",
 > +  "RTEMS_INVALID_NUMBER","RTEMS_NOT_DEFINED",
 > +  "RTEMS_RESOURCE_IN_USE",   "RTEMS_UNSATISFIED",
 > +  "RTEMS_INCORRECT_STATE",   "RTEMS_ALREADY_SUSPENDED",
 > +  "RTEMS_ILLEGAL_ON_SELF",   "RTEMS_ILLEGAL_ON_REMOTE_OBJECT",
 > +  "RTEMS_CALLED_FROM_ISR",   "RTEMS_INVALID_PRIORITY",
 > +  "RTEMS_INVALID_CLOCK", "RTEMS_INVALID_NODE",
 > +  "RTEMS_NOT_CONFIGURED","RTEMS_NOT_OWNER_OF_RESOURCE",
 > +  "RTEMS_NOT_IMPLEMENTED",   "RTEMS_INTERNAL_ERROR",
 > +  "RTEMS_NO_MEMORY", "RTEMS_IO_ERROR",
 > +  "RTEMS_INTERRUPTED",   "RTEMS_PROXY_BLOCKING"

Can this be a single column?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112487
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Reformat cpukit rtems src (!237)

2024-09-23 Thread Chris Johns (@chris)



Chris Johns started a new discussion on cpukit/rtems/src/partcreate.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112486

 >  return RTEMS_TOO_MANY;
 >}
 >  
 > -#if defined(RTEMS_MULTIPROCESSING)
 > -  if ( _Attributes_Is_global( attribute_set ) &&
 > -   !( _Objects_MP_Allocate_and_open( &_Partition_Information, name,
 > -the_partition->Object.id, false ) ) ) {
 > +#if defined( RTEMS_MULTIPROCESSING )
 > +  if (
 > +_Attributes_Is_global( attribute_set ) && !( 
 > _Objects_MP_Allocate_and_open(
 > +&_Partition_Information,
 > +name,
 > +the_partition->Object.id,
 > +false
 > +  ) )
 > +  ) {

This looks a bit average compared to the original?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112486
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Reformat cpukit rtems src (!237)

2024-09-23 Thread Chris Johns (@chris)



Chris Johns started a new discussion on cpukit/rtems/src/msgmp.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112485

 >the_packet->proxy_id  = proxy_id;
 >  
 >if ( operation == MESSAGE_QUEUE_MP_EXTRACT_PROXY )
 > - node = _Objects_Get_node( message_queue_id );
 > +node = _Objects_Get_node( message_queue_id );

Can the tool pick up a lack of `{` and `}` for the block?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112485
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Reformat cpukit rtems src (!237)

2024-09-23 Thread Chris Johns (@chris)



Chris Johns commented on a discussion on cpukit/rtems/src/clocktodtoseconds.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112482

 >  
 > -
 > -Watchdog_Interval   _TOD_To_seconds(
 > -  const rtems_time_of_day *the_tod
 > -)
 > +Watchdog_Interval _TOD_To_seconds( const rtems_time_of_day *the_tod )
 >  {
 >uint32_t time;
 >size_t   leap_year_index;
 >  
 >time = the_tod->day - 1;
 >  
 > -  leap_year_index = _TOD_Get_leap_year_index( the_tod->year );
 > -  time += _TOD_Days_to_date[ leap_year_index ][ the_tod->month ];
 > +  leap_year_index  = _TOD_Get_leap_year_index( the_tod->year );
 > +  time+= _TOD_Days_to_date[ leap_year_index ][ the_tod->month ];

I prefer no alignment. Saves wear on my space bar.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112482
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | Reformat cpukit rtems src (!237)

2024-09-23 Thread Chris Johns (@chris)



Chris Johns commented on a discussion on cpukit/rtems/src/clocktodtoseconds.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112481

 >  #include 
 >  
 >  const uint16_t _TOD_Days_to_date[ 2 ][ 13 ] = {
 > -  { 0, 0, 31, 60, 91, 121, 152, 182, 213, 244, 274, 305, 335 },
 > -  { 0, 0, 31, 59, 90, 120, 151, 181, 212, 243, 273, 304, 334 }
 > +  {0, 0, 31, 60, 91, 121, 152, 182, 213, 244, 274, 305, 335},
 > +  {0, 0, 31, 59, 90, 120, 151, 181, 212, 243, 273, 304, 334}
 >  };

Is there a reason to have the space? I do not mind as long as it is consistent.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112481
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

LibBSD | rtemsbsd/rc.conf: Show only auto interfaces in interface list (!14)

2024-09-20 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/merge_requests/14

Project:Branches: chris/rtems-libbsd:rc-conf-network-interfaces-6-freebsd-12 to 
rtems/pkg/rtems-libbsd:6-freebsd-12
Author:   Chris Johns
Assignee: Chris Johns



Show only auto interfaces in interface list. Print only the interfaces that are 
`AUTO` in the interface list as they are configured.



-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/merge_requests/14
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: LibBSD | rtemsbsd/rc.conf: Show only auto interfaces in interface list (!14)

2024-09-20 Thread Chris Johns (@chris)


Reassigned merge request 14

https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/merge_requests/14

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/pkg/rtems-libbsd/-/merge_requests/14
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

RTEMS Deployment | amd/kr26: Name the BSP kr26 (!8)

2024-09-20 Thread Chris Johns (@chris)


Chris Johns created a merge request: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/8

Project:Branches: chris/rtems-deployment:amd-kr26-bsp-name to 
rtems/tools/rtems-deployment:main
Author:   Chris Johns
Assignee: Chris Johns



Use `INHERIT` in an INI config file to create a new BSP name.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/8
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS Deployment | amd/kr26: Name the BSP kr26 (!8)

2024-09-20 Thread Chris Johns (@chris)


Reassigned merge request 8

https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/8

Chris Johns was added as an assignee.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/tools/rtems-deployment/-/merge_requests/8
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Release | Update RTEMS 6.1 release notes (!4)

2024-09-20 Thread Chris Johns (@chris)


Merge request !4 was merged
Merge request URL: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/4
Project:Branches: sebhub/rtems-release:update-rtems-6.1-release-notes to 
rtems/rtos/rtems-release:main
Author: Sebastian Huber
Assignee: Sebastian Huber

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/4
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: Release | Update RTEMS 6.1 release notes (!4)

2024-09-20 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/4#note_112399


We have the support for the 6 branch and I agree we should maintain the file. 
It is up to people to add notes.

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems-release/-/merge_requests/4#note_112399
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | cpukit/libdl/arm: Obey instruction encoding requirements for Thumb BLX (!223)

2024-09-20 Thread Chris Johns (@chris)



Chris Johns commented on a discussion: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/223#note_112398


Is the test going to be added?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/223#note_112398
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | shell/cat_file:Fix cat not outputting file with no newline at end (!219)

2024-09-20 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/219#note_112397


Maybe we should change the command to 
https://github.com/freebsd/freebsd-src/blob/main/bin/cat/cat.c?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/219#note_112397
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | SMP: Minor system start improvements (!227)

2024-09-20 Thread Chris Johns (@chris)



Chris Johns commented: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/227#note_112395


The MR's title says minor improvements but this change removes timeouts on a 
CPU starting. This is a little confusing?

-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/227#note_112395
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | SMP: Minor system start improvements (!227)

2024-09-20 Thread Chris Johns (@chris)


Merge request https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/227 
was reviewed by Chris Johns

--
  
Chris Johns started a new discussion on cpukit/score/src/percpustatewait.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/227#note_112393

 > +#include 
 > +
 > +bool _Per_CPU_Wait_for_non_initial_state( uint32_t cpu_index )

Why return anything when it is always `true` given the commit changes 
functionality by removing the timeout?

--
  
Chris Johns started a new discussion on cpukit/score/src/smp.c: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/227#note_112394

 > +if ( cpu != cpu_self ) {
 >if ( _Scheduler_Should_start_processor( assignment ) ) {
 >  started = _CPU_SMP_Start_processor( cpu_index );

This is an interface that accepts a `bool` result of the CPU starting but this 
change removes that logic from the arm BSPs. Do any of the SMP supportted arch 
detect a CPU failing to start?


-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/227
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

Re: RTEMS | aarch64/raspberrypi: improve UART (!234)

2024-09-20 Thread Chris Johns (@chris)


Merge request https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/234 
was reviewed by Chris Johns

--
  
Chris Johns started a new discussion on 
bsps/aarch64/raspberrypi/include/bsp/console/raspberrypi4b.def: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/234#note_112391

 > +/* SPDX-License-Identifier: BSD-2-Clause */

This looks like a header file. Why the `.def` extension?

--
  
Chris Johns started a new discussion on 
spec/build/bsps/aarch64/raspberrypi/objconsole.yml: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/234#note_112392

 > +  - destination: ${BSP_INCLUDEDIR}/bsp/console
 > +source:
 > +  - bsps/aarch64/raspberrypi/include/bsp/console/raspberrypi4b.def

What happens on the other RPys?


-- 
View it on GitLab: 
https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/234
You're receiving this email because of your account on gitlab.rtems.org.


___
bugs mailing list
bugs@rtems.org
http://lists.rtems.org/mailman/listinfo/bugs

  1   2   3   4   5   6   7   8   9   10   >