Change History (16)

Given that the code had never actually been through a suspend/resume cycle before, that seems like something close to a best-case result. And edge filters can be awfully nice...and it will be faster than running the GIMP on an XO...

OK... the core problem is that the bozo who wrote the camera driver put suspend/resume on the "do this after it works" list, then never quite got around to doing it. So I had to add s/r support (pretty easy) and track down a couple of subtle issues in the s/g DMA code (not so easy). The result works for me. I'll attach a patch, or it can be pulled from:

The simplest recipe I can think of is what's outlined in the description of this bug (gstreamer pipeline, then rtcwake). I haven't tested it under this simplified recipe though -- maybe there's something else at play.

Are you up to date on our general OS image? OS16 or OS17 should be about right. Maybe there is an additional problem in the Xv surface handling, and you're using an older X driver that doesn't hit it.

Most of my testing was the gstreamer/rtcwake mode. But I've been running the os17 version of runin almost nonstop working on the IRQ 48 problem, and the suspend cycles there have always worked so far.

For various reasons, I'm not actually running the os17 install; my USB key has a much older system. Booting straight os17, among other things, wants to "upgrade" my firmware into brick mode. With a bit of tweaking, though, I should be able to run the full os17 with my kernel. I'll get into that once I'm confident of my fixes for the IRQ issue.

I must admit I like the idea that it could be an xv issue and not my problem anymore :)

jon -- to prevent the auto-firmware-upgrade, do your first boot running on battery, or AC, but not both. that will suppress it that time. to suppress it permanently, rename /bootpart/boot/bootfw.zip to something else.