Hi,
Am 21.08.2015 um 03:24 schrieb aTc atc@k-n-p.org:
On 08/21/2015 02:30 AM, aTc wrote:
On 08/18/2015 09:56 PM, Dr. H. Nikolaus Schaller wrote:
Hi, I have upgraded our tree in the last weeks up to 4.2-rc7 (yesterday) and it still does not work well on the OMAP5432 EVM. The EVM does not boot properly and hangs after ~10 seconds without enlightening messsages. The 4.1 branch works fine.
I've just compiled your 4.2-rc7 kernel (with a slightly modified letux_defconfig to enable a few more drivers and features debian needs
are there some configs you can recommend to add to letux_defconfig?
), and it runs on my board.
I've also tried compiling with the plain letux_defconfig, and it runs fine as well.
There is some weirdness going on with the display though (using hdmi output, with omapdss.def_disp=hdmi on the kernel command line), with the displaymanager taking a few minutes to show up, but after that everything seems to work fine. (console works fine when the displaymanager is stopped, restarting it gives about 2 minutes of blank screen before things show up, no obvious warnings/errors in any logs)
Forget that bit, that seems to have been caused by the firewall not working properly thanks to some kernel modules i forgot to enable.
With the firewall disabled, the modified 4.2-rc7 works fine as well.
Thanks for all the tests!
I have to check what I am doing wrong. Maybe it has something to do with my broken EVM. I2C2 is broken on the hardware side and therefore I run a patched device tree to remap the I2C to GPIO pins and use the bitbang driver. This might have an influence, although it is the same with the 4.1 kernel and there it works.
So knowing that it can work is very valuable.
BR and thanks, Nikolaus
PS: the display-new warnings are because we currently use the shell-script drivers and the panel-mipi-debug driver. The others need some code cleanup.