Hi Kevin,
On 02/05/2014 04:23 PM, Kevin Hilman wrote:
On Fri, Jan 24, 2014 at 10:13 AM, Florian Vaussard florian.vaussard@epfl.ch wrote:
Hi,
On 01/24/2014 07:11 PM, Tony Lindgren wrote:
- Florian Vaussard florian.vaussard@epfl.ch [140123 01:17]:
I just tested next-20140123 with an OMAP3630 ES1.2 Overo/Tobi. Changing the include to omap36xx.dtsi do not fix the issue. I still get the external abort on non-linefetch (full log here [1]).
I think the issue here is that you need to have "ti,omap36xx" in the compatible string in addition to including omap36xx.dtsi. Otherwise "ti,omap3" will initialize things for 34xx.
For the initial minimal fix, I suggest we do something like the following. This should fix things for 36xx based tobi, then 34xx based tobi support can be added later on. Untested as I don't have one.
You are probably right. I will test Monday.
Any progress on this?
We still have the 36xx Tobi boards failing basic boot tests -next, but now also in mainline.
Thanks for the reminder. Tony's patch fixes the problem for 36xx Overo, but makes 35xx Overo to fail. I did a patch to split the Tobi between a common include file, and model-specific DTS. Will send it in a couple of minutes.
Regards,
Florian