Re: buglet in lirc_sir?

[Jarod W. <ja...@wi...>]

On Jul 8, 2009, at 12:31 PM, Christoph Bartelmus wrote:

> Hi!
>
> Jarod Wilson "ja...@wi..." wrote:
> [...]
>> Thing is.. Its plugged into ttyS0's port, so that *should* be I/O  
>> port
>> 0x03f8, not 0x03e8. LIRC_PORT is defined in lirc_sir.c as 0x3e8, but
>> the MODULE_PARM_DESC() for io says "0x3f8 or 0x2f8". One of these is
>> obviously wrong. My assumption is that its the 0x3e8 part.
>
> 0x3e8 is COM3. It's the default for lirc_sir because most internal  
> IrDA
> ports use COM3.
> Don't let the MODULE_PARM_DESC() confuse you. The given values are  
> just
> COM1 and COM2.

Ah, okay, yeah, that makes some degree of sense. Perhaps if compiling  
for the actisys dongles, it'd be better to have LIRC_PORT default to  
com1 though, since that's the most likely place it would actually be  
connected, given that they're external devices.


>> Not picking up anything with irw yet either way though. Back to
>> prodding...
>
> Try mode2 first.
> Usually you have to create a new config file when you use lirc_sir.  
> You
> most likely won't be able to use the one created with lirc_serial or
> lirc_mceusb.

Ah, okay. Thus far, I'd only tried a hauppauge rc5 remote w/its  
existing config. I'll give irrecord a go, no clue if the dongle knows  
how to handle rc5 or not... Left my main non-rc5 test remote (Motorola  
DRC800) at home, d'oh...


-- 
Jarod Wilson
ja...@wi...