On Oct 20, 2010, at 11:16 AM, HC Saustrup wrote:
> On 09-10-2010 07:09, Jarod Wilson wrote:
>> Hey folks,
>> Today, I finally got around to finishing cleanup and testing of a
>> local git branch I've had for a while that represents the road to lirc
>> 0.9.0, which has a heavy focus on compat with the lirc bits that were
>> merged upstream. Just a bit ago, I finally pushed all those bits in
>> git, after going through a battery of tests (well, some basic sanity
>> testing with a few devices and a full run of a protocol
>> encoder/decoder regression test against lirc 0.8.7). Thus far, I've
>> only tested a small handful of ir-core-based drivers, and only on a
>> 64-bit host, so any and all testing is welcomed. Going to try to do a
>> bit more testing myself, but I think I'll cut an lirc-0.9.0-pre1
>> tarball later this weekend after merging one more userspace piece (out
>> of time for tonight)... So those who aren't particularly
>> git-comfortable, you'll have to wait a few more days, but those who
>> are game for git, clone like so:
> Hi Jarod!
> I'm testing like a crazed.. well.. tester, and I managed to compile and install your 2.6.35 kernel on my box. I'm getting some sort of output from /dev/lirc0 after inserting the nuvoton_cir module, so I'm optimistic. Realizing that it doesn't speak well with the lirc 0.8.6 that comes with my Fedora 13 installation (*), I decided to try this prerelease of 0.9.0.
Nb: I'm still updating the git tree some even as I type, fixing up some things that I broke last night when merging in changes from the upstreamed lirc_dev... :)
> It seems like setup-driver.sh and configure is missing. I tried running automake, but without much luck. I'd be happy to test, but I'm a bit stuck here.
For an scm checkout, see http://lirc.org/cvs.html for details. I need to put together some web site updates to switch cvs refs to git, but the git version is like so:
git clone git://lirc.git.sourceforge.net/gitroot/lirc/lirc
(Though I typically actually do ./autogen.sh, then ./configure --with-driver=foo, then make, where 'foo' is either 'all', or 'userspace', depending on whether I want to test lirc kernel modules built from the tree, or just the ones in-kernel).
> Running updated Fedora 13 with your 2.6.35 kernel on an AsRock 330HT fitted with a Nuvoton chip.
For Fedora, I have an easier solution... :) Even for F13, you should be able to just grab and install these, and have things work:
(lirc isn't strictly needed either if you're using the mce remote, that'll be automatically decoded to input layer events)