Am 31.05.2016 um 18:21 schrieb Tony Lindgren tony@atomide.com:
- H. Nikolaus Schaller hns@goldelico.com [160530 06:31]:
I do not see it on the EVM, but on our Pyra hardware. This is strange since I use the same U-Boot (except for minor patches and nothing clock related) and the same uImage. Well, DT differs, but both are based on omap5-common.dtsi.
So there is something in the Pyra hardware which "remembers" the previous state.
Maybe we have a slightly different Palmas variant? I don't know such details.
No idea.. With omapconf you can diff the registers between two different states quite easily though.
It was easy to git clone + make on some board (because I just had it connected I did on a BeagleBoard XM).
But all I can get is:
!!! OUPS... MEMORY ERROR @ 0x00000000 !!! Are you sure that: MEMORY ADDRESS IS VALID? TARGETED MODULE IS CLOCKED?
And I was not able to get some --help from it. Is it possible that omapconf is not compatible with a 4.7-rc1 kernel?
BR, Nikolaus