tis 2014-09-23 klockan 19:03 +0200 skrev Paul Kocialkowski: > As far as I > know, the U-Boot debug UART output is hardcoded in the config as well > (CONS_INDEX), so it could be handed to the kernel correctly.
The u-boot console UART is only hardcoded in config because we haven't cared to implement multiple UART support in sunxi u-boot. But you can switch runtime between different console options (i.e. UART, netconsole or JTAG UART). > Specifying the early debug UART > through cmdline is not standard behavior. > Note that this is different from the "console" kernel cmdline parameter. > This is instead about earlyprintk. It's possible and well defined to use kernel command line arguments to specify the earlycon console and earlyprink output channel. earlycon mappes to console drivers with earlycon support, and earlyprink maps to a hardcoded list of earlyprintk drivers. > I'm pretty sure the routing specified in the fex is phony anyways. > I do wonder why setting the debug to UART0 (Luc's patch) makes my device > hang, though. Especially if it is not routed to anything. For Allwinner boot, u-boot & kernel the pinmapping specified in the FEX is applied as specified in the FEX, but only when the hardware for the section in question is activated. Also it's quite possible that the FEX file uses incorrect names for the pin mappings, as only the values matter and not their name. Regards Henrik -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
