On Tue, Mar 19, 2013 at 06:39:38AM +0000, Santosh Shilimkar wrote: > On Monday 18 March 2013 10:36 PM, Will Deacon wrote: > > Any chance you could follow up with your firmware/hardware guys about this > > please? I'd really like to understand how we end up in this state in case we > > can do something in the architecture to stop it from happening in future. > > > I will check on this part and update you when I hear from them.
Ok, thanks. Dietmar -- I seem to remember that you thought GDB did actually work with hardware breakpoints on Pandaboard across low-power states. Can you confirm/deny this please? > > Well, we could just add the warn_once prints but that doesn't stop debug > > from breaking after the first pm/suspend/hotplug operation. > > > Probably we should drop the $subject patch approach and use warn_once > at least for current rc. Ofcourse it doesn't help to get working > hw_breakpoint support. Patch end of the email with warn_once. Yeah, I'll merge that, but it's a real shame that this breaks hardware debug on one of the few platforms where it was reported to work. Will -- 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
