Re: ttyO2 broken on IGEPv2 on 3.3, 3.4-rc5 or arm-soc/for-next, working on 3.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Thomas,

Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx> writes:

> I have an IGEPv2 revision 6 board, which uses the DM3730 OMAP3. With
> 3.2 omap2plus_defconfig, the system boots fine and have a working shell
> on ttyO2. On either 3.3, 3.4-rc5 or arm-soc/for-next from Arnd, the
> system boots all the way up to showing the shell prompt, but I can't
> type any character, as if UART RX was broken.

On v3.4-rc, can you see if reverting bce492c04ba8fc66a4ea0a52b181ba255daaaf54
has any effect?

That patch had some unfortunate side effects, but I haven't seen the
problem you see, so I'm not sure if it's related.

Kevin
--
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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux