On 09/11/2022 01:35, Chris Johns wrote:
Was this posted for review? I do not remember seeing it?
Yes, on September 12.
There are a number of things that could be improved with this change.
I am sure things can be improved, but removing completely out of date
stuff can't be that bad.
--
This adds support to the CGEM driver for selection of SGMII PHY
interfaces specified via device tree parameters.
---
freebsd/sys/dev/cadence/if_cgem.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/freebsd/sys/dev/cadence/if_cgem.c
b/freebsd/sys/dev/cadence/if_cgem.c
index 047d91
This reintroduces device tree support to the CGEM driver while
preserving the ability to statically define CGEM interfaces.
---
freebsd/sys/dev/cadence/if_cgem.c | 42 +--
1 file changed, 29 insertions(+), 13 deletions(-)
diff --git a/freebsd/sys/dev/cadence/if_cgem.c
In this revised patch set, SGMII support has been reworked to use device
trees while preserving existing static instantiation used by Zynq and
Versal BSPs.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
This moves the ZynqMP BSPs over to using device trees for CGEM
instantiation now that all BSP variants provide appropriate device
trees.
---
rtemsbsd/include/bsp/nexus-devices.h | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/rtemsbsd/include/bsp/nexus-devices.h
b
Looks good and thank you for sorting out this approach.
Thanks
Chris
On 9/11/2022 8:56 am, Kinsey Moore wrote:
This adds a BSP variant for the ZynqMP BSP family to support the
Innoflight CFC-400X platform. To properly support the CFC-400X, device
trees were added to the ZynqMP platform due to b
Hello,
The following was add to the documentation build support for the RTEMS 6
release to avoid the need for us to perform mindless updates of the
documentation on each release cycle:
https://git.rtems.org/rtems-docs/tree/README.txt#n604
The text is:
10. Use the following to embed the vers
Hi,
Was this posted for review? I do not remember seeing it?
There are a number of things that could be improved with this change.
Chris
On 8/11/2022 4:47 pm, Sebastian Huber wrote:
Module:rtems-docs
Branch:master
Commit:31199e3a69d2dbd0a8f360e424fd19f3e9ef66ce
Changeset:
http://
This adds a BSP variant for the ZynqMP BSP family to support the
Innoflight CFC-400X platform. To properly support the CFC-400X, device
trees were added to the ZynqMP platform due to both the optional
management interface as well as alternate physical configuration of the
ethernet interfaces.
---
The management interface is now dynamically detected via the device
tree. The device tree also contains information pertinent to LibBSD's
ethernet configuration for all ZynqMP BSPs.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/li
Where CPU_ENABLE_ROBUST_THREAD_DISPATCH == TRUE, the only supported interrupt
level allowed to set is 0 (interrupts enabled). This constraint is enforced by
the API level functions which return an error status for other interrupt
levels.
---
.../score/cpu/riscv/include/rtems/score/cpu.h | 28
More info on this issue:
(1) the issue (internal compiler error) does not happen all the time. In
fact there are builds which even complete. The ratio failure/ok is 10/30
so far -- building in a loop 6/rtems-sparc.
(2) attempt to bootstrap with GCC failed even more miserably. At least
with
12 matches
Mail list logo