From: Tom Rini Date: Wed, 27 Mar 2013 09:57:53 -0400 Subject: [U-Boot] [PATCH 1/1 v2] omap3_beagle: Enabling UART3 first allows the Transmitter to be empty In-Reply-To: References: <1679653192.50708.1361970554739.JavaMail.ngmail@webmail21.arcor-online.net> <51447012.6010303@arcor.de> <20130319144957.GF25919@bill-the-cat> <5150C987.1040802@arcor.de> <51527A89.6070406@arcor.de> Message-ID: <20130327135753.GO5711@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Mar 27, 2013 at 10:29:00AM +0100, Javier Martinez Canillas wrote: > On Wed, Mar 27, 2013 at 5:50 AM, Manfred Huber wrote: > > Please test the Patch. It is very simple on a Beagleboard. I guess you > > have flashed the actual SPL and u-boot and Beagleboard boots correctly. > > Now press and hold 'User' button and connect power. SPL should hang. > > You can see some symbols on the console from the ROM code. > > > > Hi Manfred, > > I don't have access to my IGEP board right now but I'll test your > patch as soon as posible. > > > Install the Patch, compile it and flash the NAND. Beagleboard still > > boots correctly. Now press and hold 'User' button again and Beagleboard > > should also boot correctly. The Patch works. > > > > I suspect the IGEP board has the same bug. If so, the Patch should work > > on this board too and we don't need CONFIG_SYS_NS16550_BROKEN_TEMT > > anymore. > > > > I still think that we should keep CONFIG_SYS_NS16550_BROKEN_TEMT or > something similar instead of just checking for CONFIG_OMAP34XX. Since > we don't know if this problem is also present on other TI OMAP > platforms (or any other platform). I would just change > CONFIG_SYS_NS16550_BROKEN_TEMT semantics once is confirmed that this > also fixes the issue on IGEP boards. I'm attempting to see if this ROM bug is (a) known and (b) is or was fixed at some point. Based on what I know (or at least think I know) of how the ROM code lived for "OMAP3", given that you're seeing this on beagle and igep, it's a valid assumption that OMAP34XX is buggy. The question I have (and hope for resolution on) is if it's a problem on am335x/omap4 or later as well. If I follow how to reproduce this issue (and I think I do), assuming I can I'll setup an am335x platform in a similar position. > > If you don't want a patch for this bug please let me know. I will not > > bother you again. > > > > Thanks a lot for working on this. Some people work on mainline U-Boot > on their free time (like myself) so it can take a few days until you > get a response about a patch. Please be patient :-) Yes, thanks for working this issue through, I also appreciate it! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: