From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manfred Huber Date: Fri, 29 Mar 2013 09:33:47 +0100 Subject: [U-Boot] [PATCH 1/1 v2] omap3_beagle: Enabling UART3 first allows the Transmitter to be empty In-Reply-To: <5154033D.6090003@gmail.com> References: <1679653192.50708.1361970554739.JavaMail.ngmail@webmail21.arcor-online.net> <51447012.6010303@arcor.de> <20130319144957.GF25919@bill-the-cat> <5150C987.1040802@arcor.de> <5152F60E.50600@gmail.com> <5153DDEC.6030300@arcor.de> <5154033D.6090003@gmail.com> Message-ID: <515551EB.8020405@arcor.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 28.03.2013 09:45, schrieb Andreas Bie?mann: > Dear Manfred Huber, > > On 03/28/2013 07:06 AM, Manfred Huber wrote: >> On 2013-03-27 14:37, Andreas Bie?mann wrote: > > > >>> On 03/25/2013 11:02 PM, Manfred Huber wrote: > > > >>>> + serial_out(UART_LCR_DLAB, &com_port->lcr); >>>> + serial_out(baud_divisor & 0xff, &com_port->dll); >>>> + serial_out((baud_divisor >> 8) & 0xff, &com_port->dlm); >>>> + serial_out(UART_LCRVAL, &com_port->lcr); >>>> + serial_out(0, &com_port->mdr1); >>> > I wonder which use-case requires UART flushing in u-boot context before > initializing the UART for u-boot correctly. Can someone explain this to > me? Shouldn't we always start here from the very beginning and setup > UART as configured? Beagleboard has several ways to boot (NAND, SD/MMC, UART, ...). For the boot mode with UART, Beagleboard configures the UART and ends with a non empty transmitter. In a booting sequence where UART is before NAND, SD/MMC or wherever SPL starts from, we have not a clean UART. > >> >> It's not critical. So I guess it's not needed for this release. > > Well, if there are boards in the field that will not boot with the next > release I think it is critical. > We do have some omap3 (omap35xx and am37xx) based boards here. I can > recall a situation where some few boards did not boot from sd-card while > serial debug cable was attached (AFAIR this was not the case when > booting from NAND). The root cause was never investigated, so maybe we > suffered exactly this bug. Can you test this boars with my patch? > > Best regards > > Andreas Bie?mann >