On 17 December 2014 at 22:13, Nishanth Menon <n...@ti.com> wrote: > I do realize that i did have different opinion given bootloader screw > ups. Given that we have discovered a potentially bad configuration (in > this case for some reason almost ALL TI platforms "have bad > configuration" - could be due to recent clock code changes or what > ever), just killing boot does not make sense to me as purely > bootloader being the cause may not always be the case for that path to > go wrong.
Sorry, I still *disagree*. Its not about bootloaders getting screwed up.. Yes, bootloader was indeed running at a frequency not listed in kernel. But we *tried* our best to get that resolved and we failed to change frequency. We *shouldn't* allow kernel to move a inch further. It might be dangerous for the platform to continue further as we are talking about the almighty CPU. So, the bug is still the right way forward, atleast for me. -- viresh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
