Hi Magnus,
On Thu, Aug 25, 2016 at 4:42 AM, Magnus Damm <magnus.damm@xxxxxxxxx> wrote:
> On Wed, Aug 24, 2016 at 9:58 AM, Kuninori Morimoto
> <kuninori.morimoto.gx@xxxxxxxxxxx> wrote:
>> I noticed that Lager "ES3.0" board can't boot on this and previous -rc2 branch.
>> In my and Shimoda-san's check, "ES2.0" seems have no problem.
>>
>> It start works if I reverted this patch.
>>
>> 09a28bb8b17e8cab3e9c120b7e37f631cc334a8f
>> ("ARM: dts: lager: use demuxer for IIC3/I2C3")
>
> FYI, I have now received the problematic Lager ES3 board from
> Morimoto-san and I will install it for remote access.
>
> How can we check which ES version we are running? I recall seeing some
> patch from Geert that printed out useful information during boot, any
> chance that could make it upstream (if it is not already)?
It's part of my topic/renesas-debug branch. Just merge that into latest
renesas-drivers and see...
Note that that branch also has the debug code to disable unused MSTP
clocks during boot. If you only want the SoC identification, just cherry-pick
commit c8e302adee4a1f9c ("[LOCAL] soc: renesas: Print SoC Product Version").
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
