I am a newbie that's been trying to research for the past two weeks and am burnt out.  I am needing some advice to get started on compiling something for the XBox IR Remote (very cheap on ebay).

My target machine IS NOT an XBox, but rather an ARM7 compatible processor (EP7312), embedded Linux running 2.4.18-rmk7.  I currently have an ATI Remote Wonder I running on this (I was able to compile ati_remote.c for this) and it is controlling my jukebox program that runs on it.

I have a request of acquaintances to enable this XBox Remote to run on this embedded device ( Ebay Pic ) and have been researching here and there to see how I may be able to get this running.  Here is what I've done so far:

1) I've wired up the remote with a regular USB cable so it would connect to my ARM7 device.
2) I tested the IR on a Windows laptop with drivers I downloaded from here http://www.redcl0ud.com/xbcd_rc.html  It works fine on Windows, so I know the wiring is correct.
3) I plug in the device to the ARM7 device and run dmesg to see what's happening.  Here is what I get.

<6>hub.c: USB new device connect on bus1/1/1, assigned device number 8
usb.c: USB device 8 (vend/prod 0x45e/0x284) is not claimed by any active driver.
CONFIGURED HOTPLUGGING


=========================

I know I somehow need to load a driver for this XBox IR receiver, or get some other thing running that can read signals from this remote.

If I can get a driver, I can create a device node and read from it - but not knowing where to start, I went with lirc.

I have constructed a tool chain (crosscompiler) that has successfully compiled the ati_remote.c in the past.  (gcc-2.95.3 - glibc-2.2.3 for the 2.4.18-rmk7 kernel that matches the kernel currently in use).  I tried to download lirc-0.8.5 but cannot compile anything for it, so I downloaded lirc-0.8.4a.

Now I'm stuck -- I understand that I am to select lirc_atiusb as the driver, but I have no idea what other parameters to provide.  Here is what I have for the configure command:

make clean

export PATH=/opt/crosstool/gcc-2.95.3-glibc-2.2.5/arm-softfloat-linux-gnu/bin/:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/opt/bin:/usr/local/games:/opt/jdk1.5.0_06//bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/xfce4/bin

./configure CC=/opt/crosstool/gcc-2.95.3-glibc-2.2.5/arm-softfloat-linux-gnu/bin/arm-softfloat-linux-gnu-gcc CFLAGS="-Os -Wall -static" --build=arm-softfloat-linux-gnu --host=arm --target=arm --with-kerneldir=/opt/crosstool/gcc-2.95.3-glibc-2.2.5/arm-softfloat-linux-gnu/arm-softfloat-linux-gnu/include/ --includedir=/opt/crosstool/gcc-2.95.3-glibc-2.2.5/arm-softfloat-linux-gnu/arm-softfloat-linux-gnu/ --with-moduledir=/opt/crosstool/gcc-2.95.3-glibc-.2.5/arm-softfloat-linux-gnu/lib/ --without-x --with-driver=atiusb

make

But I don't make it to the 'make' portion because configure bombs out with this error:

....
checking linux/i2c-dev.h usability... yes
checking linux/i2c-dev.h presence... yes
checking for linux/i2c-dev.h... yes
configure: error: *** you need to have the Linux kernel source installed
        for this driver

me@vector1:lirc-0.8.4a$ _

=============

Can someone kindly point me in the correct direction as to where to get started?  I have no idea what linux source it's looking for, if it's not the one that's bundled with the crosscompiler.  Am I missing other parameters that should be supplied? Or am I going about this in an entirely wrong fashion?  Is LIRC not the correct way to go?

Sorry for the long mail:

The target computer is a DMP1 car MP3 Jukebox running at 90MHz and has 16 Mb of RAM, 4 Mb of ROM, 60 GB harddrive (I upgraded it).  It is running a community-supported version of a jukebox player called "openfi," which I further hacked to make it work with an ATI Remote Wonder I.  I have no experience with Lirc prior to this project.

The build computer is a HP Vectra VL, 512 MB ram, running at 500 MHz with 40 GB harddrive.  It is running a flavor of Vector Linux with three crosscompilers that I built for it.  The one I feel I need to use is the gcc-2.95.3-glibc.2.3.3 toolchain because that is the one the kernel was compiled with.

Any help / suggestion / wisdom is appreciated.  Even criticisms.

Thank you,

~lum