Hi,
I'm currently trying to develop a IR Remote (TV consumer) listener in C under Linux.
First of all I tried with an old notebook with an integrated IR peripheral (FIR)under Debian (kernel 2.6). All seems to work fine, I can also access directly with
#cat /dev/ttyS1
And my listener (written in C) work pretty fine.
Problems came up with a newer notebook with Ubuntu 8.10.
I set FIR in Bios like the older notebook. But trying to access with cat /dev/ttyS1 raise this error: read: Input/output error
I took immediatly that something lock this device but, how can I see which process lock this resource?
Running my program (a simple non canonical read from the /dev/ttyS1) give me NO data... Seems to be that nothing is coming through the IR port (despite I was trying clicking about an hundred buttons on 3 differents remote controllers :) ).
I tried to unload all modules of irda and I disable UART setting with setserial, but nothing change.
I'm pretty sure that problem came because of "something" who lock this device, but I have no idea how to patch it.
Any suggestions?
Thanks a lot
Sergio
I'm currently trying to develop a IR Remote (TV consumer) listener in C under Linux.
First of all I tried with an old notebook with an integrated IR peripheral (FIR)under Debian (kernel 2.6). All seems to work fine, I can also access directly with
#cat /dev/ttyS1
And my listener (written in C) work pretty fine.
Problems came up with a newer notebook with Ubuntu 8.10.
I set FIR in Bios like the older notebook. But trying to access with cat /dev/ttyS1 raise this error: read: Input/output error
I took immediatly that something lock this device but, how can I see which process lock this resource?
Running my program (a simple non canonical read from the /dev/ttyS1) give me NO data... Seems to be that nothing is coming through the IR port (despite I was trying clicking about an hundred buttons on 3 differents remote controllers :) ).
I tried to unload all modules of irda and I disable UART setting with setserial, but nothing change.
I'm pretty sure that problem came because of "something" who lock this device, but I have no idea how to patch it.
Any suggestions?
Thanks a lot
Sergio
Comment