On Wed, Jan 6, 2010 at 5:00 AM, Harald Gustafsson <hgu1972@xxxxxxxxx> wrote: > Hi, > > Thanks for working on improving the Nova T 500 performance, it is much > appreciated, and let me know if you need further help with debugging it. > > I tried your dib0700-ir tree. My problems with the Nova T 500 and the 1.20 > firmware have been warm reboots. Before your patch a warm reboot would give > I2C errors in dmesg log with the 1.20 FW, hence I have only used my machine > with cold boots since my upgrade this xmas. With the 1.10 FW and Ubuntu 7.04 > + v4l tip sometime in 2008 the system have run without much problems > including frequent warm reboots for 2 years. Sorry to say this patch does > not solve the problem to have a working IR after a warm reboot see dmesg > logs below. I have not seen any problems with high load before, so can't > give any info on that matter more than it is certainly low now. The I2C > errors I saw before your patch come shortly after a warm reboot (see last > dmesg log included), but have not had any problems after cold boots for the > past week the system have been recording. Hi Harald, Thanks for taking the time to test and provide feedback. Just to be clear, this patch does *not* address the warm reboot problem. I am continuing to work that issue, but there should be no expectation that this patch allows the device to survive a warm reboot. It should address concerns people were seeing where the system load would be between 0.50 and 1.0 just by having the device connected, and *may* help in cases where you start to see mt2060 errors after several hours of operation. Cheers, Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
