The sun5i defconfig default of CONFIG_SW_DEBUG_UART=1 is wrong on all devices except for those who use CONS_INDEX=2 in uboot. In others, both A10s as A13, it leads to a system which hardlocks.
UART0 with the default pinmux can never lead to a working UART on A13, as these pins are not available on the A13 package. When the A13 based device has its accessible UART on UART1, then the UART0 setting does not hurt, it just does not give you a working early UART, but that does not prohibit the system from booting. When U-Boot has been set to use FEL/SDCON, then the UART0 pinmux will have been set to sd pins, and then this setting becomes valid again. Signed-off-by: Luc Verhaegen <l...@skynet.be> --- arch/arm/configs/sun5i_defconfig | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/arm/configs/sun5i_defconfig b/arch/arm/configs/sun5i_defconfig index da0e418..aae0561e 100644 --- a/arch/arm/configs/sun5i_defconfig +++ b/arch/arm/configs/sun5i_defconfig @@ -42,7 +42,7 @@ CONFIG_KARMA_PARTITION=y CONFIG_EFI_PARTITION=y CONFIG_CFQ_GROUP_IOSCHED=y CONFIG_ARCH_SUN5I=y -CONFIG_SW_DEBUG_UART=1 +CONFIG_SW_DEBUG_UART=0 CONFIG_SWP_EMULATE=y CONFIG_PREEMPT=y CONFIG_AEABI=y -- 1.7.7 -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
