Hi, On Thu, Feb 9, 2012 at 3:30 PM, Felipe Contreras <felipe.contreras@xxxxxxxxx> wrote: >> Again, I'm totally confused as to _WHY_ this needs to be y. What is >> causing this oops without it? If an oops is happening, then shouldn't >> this be a strict dependancy? Why allow it to be disabled at all if it >> can break your box if you don't enable it? > > It's not an oops, it's a warning, and again, it depends on the > firmware being used. We don't have control over that, and we have no > way to detect if this feature is there. It's up to the user. I have been thinking more into it, how about looking for a WDT symbol inside the baseimage to decide whether to turn ON/OFF WDT3, this would mean that the code is always compiled in, but the decision to turn it on/off is made at runtime. Regards, Omar -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
