Hi Tomaž, On Tue, Mar 05, 2019 at 10:13:04AM +0100, Tomaž Šolc wrote: > On 4. 03. 19 09:04, Sascha Hauer wrote: > > So that said, even with a debug UART enabled for Rpi1 we should still > > allow to build for Rpi2/3 although we know it won't work there. > > > > The reason is you might get failures only when multiple SoCs are > > selected. In that case you only want to enable early debugging support > > (for the SoC you are currently testing on) without changing other things > > in the config which might make your errors disappear. > > Thanks for the clarification. I've sent another patch series that removes > the restriction for board builds and adds the help text. > > On the topic of the debug UART, I've also noticed that it's a bit tricky to > get it running on Raspberry Pi 3. The problem is that the debug UART is > using PL011 hardware, but the console is now using miniuart. > > In addition to enabling it in menuconfig, I have to reverse the commit > ab76f9d0 (switch to miniuart for stdout in the device tree) and keep > "dtoverlay=pi3-miniuart-bt" in "config.txt" (instruction for this was > removed in f1330536). I just sent a series based on your patches adding mini UART support for the rpi3. I need the basic ns16550 early debugging code for Layerscape anyway, so it's a win-win ;) Tested on Layerscape, but not on rpi3, so I would be glad if you could test it. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
