-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to RTEMS 6 with Libbsd and Legacy net support #61
base: master
Are you sure you want to change the base?
Conversation
I have reviewed the CI failures and I do not think they are related to the changes I have made. |
I just pushed a change to the master branch here which cleaned up some compiler warnings, and the subsequent CI build jobs for RTEMS 4.9 and 4.10 both succeeded. I also re-triggered those CI builds for this PR which unfortunately both failed again, so some code change inside this PR must have caused the failures. I don't care about the pre-commit check failure, just the ability to build this module against RTEMS 4.9 and 4.10. Note that the EPICS Base 7.0 version that this CI is using at the moment doesn't include your RTEMS-6 PRs, and we expect future releases of this module to continue to build against older EPICS versions anyway — the CI jobs that build it for Linux against both 3.14 and 3.15 should hint at that. |
29a2d9e
to
1a65c02
Compare
@anjohnson I have resolved the issue with 4.10 and I assume 4.9. It seems the define |
Unfortunately, when I try to compile (MVME6100 legacy RTEMS6) I get this: |
e.g. in devIocStats/os/RTEMS/devIocStatsOSD.h But then I get this error: |
ok, found this: |
The |
Works with the current RTEMS6 master(main). rtems_libio_count_open_iops is defined there. |
Thanks for confirming this. I do not know what the approval for workflows means. |
@simon-ess will have to speak up if he cares about the clang-format failure (those checks seem rather obnoxious to me), but this looks good for the RTEMS builds, thanks! |
I would prefer that the formatting check pass; otherwise it should be disabled, since we would then be just ignoring a failing test. We could discuss exactly what the best formatting is, but I don't like the idea of letting it fail. |
I had no idea there was a coding standard. I am happy to take a look.
This makes sense. I can fix it. |
1a65c02
to
a5ccfbe
Compare
I have pushed changes to fix the formatting. I did the changes manually from the diff in the CI log. Is this OK? |
I found a problem when I wanted to use iocStats for beaglebone black (arm). +int devIocStatsGetClusterUsage(int pool, int pval) { return -1; } /* This would otherwise need _KERNEL to be defined... */ |
This pull request adds support for RTEMS 6 for the legacy network and libbsd.
It needs a current build of RTEMS 6 and tools.