Mark,

I am sincerely grateful for your work on this, and I just can't wait to do some testing for you. Unfortunately, I'm in the middle of a ton of work right now and I just can't get a good couple of hours free to work with it. It may be a month or so before I can get to it, but I definitely will, and I'll post the results.

Thanks again,

Greg Haase

Mark Weaver wrote:

Changelog (from http://www.blushingpenguin.com/mark/blog/?p=18):

- Use schedule_timeout not mdelay as mdelay is a busy loop. This fixes high CPU usage during IR sending. - Drop out of the polling loop when the chip is ready rather than after 1s (can’t believe I didn’t notice this one!). This greatly speeds sending. Fiddle with gap parameter in lircd.conf to avoid confusing the device you are controlling (for reference, it's in microseconds and I use 1/3s ~ gap 333333).

Original HOWTO at http://www.blushingpenguin.com/mark/blog/?p=17

This has been working well for me for nearly two weeks, although no-one else has had any luck! Testing feedback welcome.

Thanks,

Mark


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to