Yeah go ahead, thanks Jan.
On Mon, Mar 15, 2021 at 6:58 AM Joel Sherrill <j...@rtems.org> wrote: > > If this matches the state of the got master, then ok. > > On Mon, Mar 15, 2021, 7:55 AM <jan.som...@dlr.de> wrote: >> >> Could someone please have a look at this patch? >> >> > -----Original Message----- >> > From: Sommer, Jan >> > Sent: Friday, March 5, 2021 7:04 PM >> > To: devel@rtems.org >> > Cc: Sommer, Jan <jan.som...@dlr.de> >> > Subject: [PATCH v2] user/bsps: Mention fixed console baud rate for zynq >> > >> > --- >> > user/bsps/arm/xilinx-zynq.rst | 12 ++++++++++++ >> > 1 file changed, 12 insertions(+) >> > >> > diff --git a/user/bsps/arm/xilinx-zynq.rst b/user/bsps/arm/xilinx-zynq.rst >> > index 365c336..29f9cb0 100644 >> > --- a/user/bsps/arm/xilinx-zynq.rst >> > +++ b/user/bsps/arm/xilinx-zynq.rst >> > @@ -37,6 +37,18 @@ to return the peripheral clock. Normally this is half >> > the >> > CPU clock. This function is declared ``weak`` so you can override the >> > default >> > behaviour by providing it in your application. >> > >> > +Console >> > +------- >> > + >> > +The console driver for the UARTs will always be initialized to a baud >> > +rate of 115200 with 8 bit characters, 1 stop bit and no parity bits >> > +during start up. >> > +Previous configurations programmed into the hardware by the Xilinx >> > +tools or a bootloader will be overwritten. >> > + >> > +The settings for the console driver can be changed by the user >> > +application through the termios API afterwards. >> > + >> > Debugging with xilinx_zynq_a9_qemu >> > ---------------------------------- >> > >> > -- >> > 2.17.1 >> >> _______________________________________________ >> devel mailing list >> devel@rtems.org >> http://lists.rtems.org/mailman/listinfo/devel > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel