RE: stuck with lirc_sir

[gis <gis...@wa...>]

Thanks for your help, Karl.

Actually, nothing happens, and I'm not even getting close to a solution...

What I did was recompiling the kernel with serial port driver as module... I
also disabled all irda drivers.
Then after reboot, I done :

# setserial /dev/ttyS3 uart none

( I did it also with ttyS0 ttyS1 ttyS2... just to be sure. )

I tryed also 

# rmmod serial

But same conclusion, mode2 still tells me nothing.
I'm sure I'm missing something, like linking lirc_sir to the tty...

What command can I run to debug a little bit more ?

The /proc/interrupts just tells me that lirc_sir is running on IRQ7, so what
?


Thank you.
Gis.
 



-----Original Message-----
From: Karl Bongers [mailto:ka...@tu...] 
Sent: samedi 24 janvier 2004 02:31
To: lir...@li...
Cc: gis...@wa...
Subject: Re: stuck with lirc_sir

On Fri, Jan 23, 2004 at 11:34:28AM +0100, gis wrote:
> Hello,
> I'm using kernel 2.4.22 on a Toshiba laptop, so there's some tweaking I
> found to activate the SMC IRDA card, using toshsat1800-smcinit.  it ends
> with this :


> > # cat /var/log/syslog
> > Jan 23 10:57:14 toshix toshsat1800-irdasetup: toshsat1800-irdasetup 0.2
> > Jan 23 10:57:14 toshix toshsat1800-irdasetup: LPC47N227 chip (ver 0x29,
> > Jan 23 10:57:14 toshix toshsat1800-irdasetup: set sirbase=0x2e8,
> firbase=0x2f8, dma=3, irq=7
> > Jan 23 10:57:14 toshix toshsat1800-irdasetup: set UART 2 IR mode to
IrDA,
> auto powerdown on and powered up
> > Jan 23 10:57:14 toshix toshsat1800-irdasetup: LPC47N227 chip (ver 0x29,
> rev 0x0) configuration successfully ended
> > Jan 23 10:57:14 toshix toshsat1800-irdasetup: PCI device 0x10b9:0x1533
not
> found
> > # findchip -v
> > Found SMC FDC37N869 Controller at 0x3f0, DevID=0x01, Rev. 0
> >    SIR Base 0x2e8, FIR Base 0x2f8
> >     IRQ = 7, DMA = 3
> >     Enabled: yes, Suspended: no
> >     UART compatible: yes
> >    Half duplex delay = 3 us


> I installed lirc configured on lirc_sir driver at 0x3f0 with no problem
> except this warning during make :


> > lirc_sir.c:56:2: attention : #warning
> "******************************************"
> > lirc_sir.c:57:2: attention : #warning " Your serial port driver is
> compiled into "
> > lirc_sir.c:58:2: attention : #warning " the kernel. You will have to
> release the "
> > lirc_sir.c:59:2: attention : #warning " port you want to use for LIRC
> with:      "
> > lirc_sir.c:60:2: attention : #warning "    setserial /dev/ttySx uart
none
> "
> > lirc_sir.c:61:2: attention : #warning
> "******************************************"


> ( I don't understand If I'm using /dev/lirc or /dev/ttySx ..  And also
which
> ttyS ??? )

/dev/lirc is owned by lirc_serial.o, so when you access it you talk
to lirc_sir.o.
/dev/ttyS3 is owned by serial.o.

Both drivers are designed to operate on the same hardware(16550/8250 UART).
Only one can be active on the hardware at any one time.

You need to tell serial.o to free up the hardware if it is compiled in:
setserial /dev/ttyS3 uart none
And you don't want the any irda driver loaded.

> Anyway, then I modprobe lirc_sir :
> > lirc_sir: I/O port 0x02e8, IRQ 7.
> > enable_irq(7) unbalanced from c8b15aad
> > lirc_sir: Installed.
> But then, when I mode2 or irrecord, nothing happens.

mode2 is the best starting point to bring up lirc_sir or lirc_serial.
mode2 simply displays any data available from lirc_sir, the data
is timing of remotes signals(run length encoded pulse/spaces in useconds).

you can look at /proc/interrupts to see if any interrupts are happening,
which they should when data goes in or out.

Hope that helps.

Karl.