On 7/7/21 12:03 pm, Kinsey Moore wrote: > On 7/6/2021 20:57, Chris Johns wrote: >> On 7/7/21 11:05 am, Kinsey Moore wrote: >>> The need for the difference on ZynqMP is that there are 4 different CGEM >>> interfaces of which dev boards primarily make use of CGEM3. >> RTEMS_BSD_DRIVER_XILINX_ZYNQMP_CGEM0(ZYNQMP_IRQ_ETHERNET_0); >> RTEMS_BSD_DRIVER_XILINX_ZYNQMP_CGEM1(ZYNQMP_IRQ_ETHERNET_1); >> RTEMS_BSD_DRIVER_XILINX_ZYNQMP_CGEM2(ZYNQMP_IRQ_ETHERNET_2); >> RTEMS_BSD_DRIVER_XILINX_ZYNQMP_CGEM3(ZYNQMP_IRQ_ETHERNET_3); >> >> ? > > Yes, this does technically work
Hmm, I suggest this is what we should support as a default. > if you can read the shell output past the log > spam. The other interfaces trying and failing to come up throw a gargantuan > amount of messages to the console. Why do these interfaces fail to initialise? What are the errors? The removed probe check is based around FDT and so I suspect is the reason Sebastian suggested FDT support. Needing FDT support would break existing Zynq users. Maybe we need something more in the probe conditional for RTEMS to see if clocks or other related pieces of the hardware are set up? There maybe a relationship between the FSBL and the errors you are seeing. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
