> What does the device actually use for debug port? > > The fex file in sunxi-boards says:
This is not used at all by the kernel. The debug port is hardcoded in the defconfig and set up very early (in early ASM code). > uboot could presumably include the debug uart specification it set up > in the kernel commandline of the default environment but this will not > work with customized environment or boot.scr It may even be too early to parse the command line. In addition, why would a customized environment or boot.scr change anything? 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. I don't think it is a clean solution though. 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. > Are the unused uart1 lines muxed to PE by default? These are > supposedly connected to camera on Ampe. Maybe setting up all the uarts > in u-boot just in case would work? We do not have a fex file that uses > PE for uart so far. 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. -- Paul Kocialkowski, Replicant developer Replicant is a fully free Android distribution Website: http://www.replicant.us/ Redmine: http://redmine.replicant.us/
signature.asc
Description: This is a digitally signed message part
