* Troy Benjegerdes <hozer@xxxxxxxxx> [160207 21:31]: > On Mon, Feb 08, 2016 at 05:09:07AM +0000, Paul Walmsley wrote: > > On Sun, 7 Feb 2016, Troy Benjegerdes wrote: > > > > > Well after turning off CONFIG_FIT in u-boot, I sat staring at > > > 'Starting kernel ...' and then a root login popped up. > > > > Good! > > > > > So it does not seem to like 'console=ttyS2,115200n8' very much.. and for > > > that matter ttyO2 doesn't work either... hrrm. > > > > According to my old boot script, it should be ttyO2. > > well, I guess I just proved that tty02 doesn't work, but > when you finally look real close ttyO2 does... > > Now weren't we supposed to switch to ttyS2 naming > conventions a long time ago? Both should work, you need to check your .config options. If you have CONFIG_SERIAL_8250_OMAP set, then that takes over and omap-serial is never probed. The ttyO2 kernel cmdline gets translated to ttyS2, you still need to update the userspace to use the right console though. So we still don't have a solution fro dropping omap-serial. > > > Now to figure out if I can make LCD/omapfb work again... > > > > > > (FYI, it seems 3.14-3.18 mainline series kernels would work with the > > > am3517-evm with 'nohlt' on the command line without a device tree) > > > > Ah, the good old days.. > > Well, at least I don't have to write a bunch of C code because the > interrupts are wired differently. Now I just have to debug all this > device tree .... I don't think I ever used nohlt with the am3517-evm. Or if I did it was saved in the u-boot environment. But yeah, 3517 we should be able to support as well as other omap3 as they are very similar. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
