Maxim Levitsky | 2 May 00:52 2010
Picon

lirc_dev: generic implementation of LIRC_{GET|SET}_SEND_MODE V2

How about this: 

    lirc_dev: create generic implemenation of LIRC_SET_SEND_MODE and LIRC_GET_SEND_MODE
    and obsolete its use

    This adds generic implementation of these  ioctls
    and removes it from drivers that already use the lirc_dev->features
    It also obsoletes this feature, because it isn't used

    Signed-off-by: Maxim Levitsky <maximlevitsky@...>

diff --git a/daemons/hw_default.c b/daemons/hw_default.c
index 73ed18a..302a620 100644
--- a/daemons/hw_default.c
+++ b/daemons/hw_default.c
 <at>  <at>  -40,23 +40,6  <at>  <at> 

 extern struct ir_remote *repeat_remote;

-static unsigned long supported_send_modes[]=
-{
-	/* LIRC_CAN_SEND_LIRCCODE, */
-	/* LIRC_CAN_SEND_MODE2, this one would be very easy */
-	LIRC_CAN_SEND_PULSE,
-	/* LIRC_CAN_SEND_RAW, */
-	0
-};
-static unsigned long supported_rec_modes[]=
-{
-	LIRC_CAN_REC_LIRCCODE,
(Continue reading)

Christoph Bartelmus | 2 May 09:30 2010
Picon

Re: lirc_dev: generic implementation of LIRC_{GET|SET}_SEND_MODE V2

Hi!

Maxim Levitsky "maximlevitsky@..." wrote:

> How about this:
[...]

I'd leave this in:

> -static unsigned long supported_send_modes[]=
> -{
> -	/* LIRC_CAN_SEND_LIRCCODE, */
> -	/* LIRC_CAN_SEND_MODE2, this one would be very easy */
> -	LIRC_CAN_SEND_PULSE,
> -	/* LIRC_CAN_SEND_RAW, */
> -	0
> -};
> -static unsigned long supported_rec_modes[]=
> -{
> -	LIRC_CAN_REC_LIRCCODE,
> -	LIRC_CAN_REC_MODE2,
> -	/* LIRC_CAN_REC_PULSE, shouldn't be too hard */
> -	/* LIRC_CAN_REC_RAW, */
> -	0
> -};
> -
>  struct hardware hw_default=
>  {
>  	LIRC_DRIVER_DEVICE, /* default device */
>  <at>  <at>  -286,64 +269,9  <at>  <at>  int default_init()
(Continue reading)

Maxim Levitsky | 2 May 15:08 2010
Picon

Re: lirc_dev: generic implementation of LIRC_{GET|SET}_SEND_MODE V2

On Sun, 2010-05-02 at 09:30 +0200, Christoph Bartelmus wrote: 
> Hi!
> 
> Maxim Levitsky "maximlevitsky@..." wrote:
> 
> > How about this:
> [...]
> 
> 
> I'd leave this in:
First I didn't understand you, but now I get it,
you want lirc to see if kernel driver is supported.
I agree with that.

> 
> > -static unsigned long supported_send_modes[]=
> > -{
> > -	/* LIRC_CAN_SEND_LIRCCODE, */
> > -	/* LIRC_CAN_SEND_MODE2, this one would be very easy */
> > -	LIRC_CAN_SEND_PULSE,
> > -	/* LIRC_CAN_SEND_RAW, */
> > -	0
> > -};
> > -static unsigned long supported_rec_modes[]=
> > -{
> > -	LIRC_CAN_REC_LIRCCODE,
> > -	LIRC_CAN_REC_MODE2,
> > -	/* LIRC_CAN_REC_PULSE, shouldn't be too hard */
> > -	/* LIRC_CAN_REC_RAW, */
> > -	0
(Continue reading)

Jongi | 2 May 23:07 2010
Picon

mplayer - failed to open lirc support

I am running Debian Sid with the following lirc packages

# dpkg -l | grep lirc
ii  liblircclient-dev                    0.8.6-1~c0.sidux.13           infra-red remote control support - client library development fi
ii  liblircclient0                       0.8.6-1~c0.sidux.13           infra-red remote control support - client library
ii  lirc                                 0.8.6-1~c0.sidux.13           infra-red remote control support
ii  lirc-modules-2.6.31.11               0.8.6-1~c0.sidux.13+jng1      Linux Infra-red Remote Control support (binary kernel modules)
rc  lirc-modules-2.6.32-4-amd64          0.8.6-1~c0.sidux.13+2.6.32-11 Linux Infra-red Remote Control support (binary kernel modules)
ii  lirc-modules-source                  0.8.6-1~c0.sidux.13           infra-red remote control support - kernel modules
ii  lirc-x                               0.8.6-1~c0.sidux.13           infra-red remote control support - X utilities

I have a lircrc setup as follows

mythtv-debian:/home/mythtv# ls -la .mplayer/lircrc
lrwxrwxrwx 1 mythtv mythtv 17 2009-04-10 01:50 .mplayer/lircrc -> ../.mythtv/lircrc

mythtv-debian:/home/mythtv# ls .mythtv/lircrc
.mythtv/lircrc

However the remote works under MythTV but doesn't under mplayer. The following error is returned:

Failed to open LIRC support. You will not be able to use your remote

The mplayer version I am using is from the debian multimedia repo.

ii  mplayer                              1:1.0.rc2svn20100313-0.0      The Ultimate Movie Player For Linux

Before I upgraded to 0.8.6 lirc the same mplayer was working with my remote. Could the problem be related to 0.8.6 creating /var/run/lirc/lircd?


    
------------------------------------------------------------------------------
gerard | 3 May 20:18 2010

installing lirc on mandriva

Hi the list.

I am new here, and I am trying to use a IBM laptop with Mandriva 2010 to catch
IR signals froms various remotes which are not in the database (I'd like to add
them to the database).

I installed many packages
rpm -qa|grep lirc
kdelirc-4.3.5-0.4mdv2010.0
dkms-lirc-0.8.6-2mdv2010.0
libkdelirc_shared1-4.3.5-0.4mdv2010.0
lirc-0.8.6-2mdv2010.0
liblirc0-0.8.6-2mdv2010.0
dkms-lirc-gpio-0.8.6-2mdv2010.0
lirc-remotes-0.8.3-0.20080704.4mdv2010.0
lirc-kernel-2.6.31.12-server-1mnb-0.8.6-2mdv2010.0

I rebooted, and made some tries :
lirc daemon is working

ls /dev/li* ->nothing

irrecord
Usage: irrecord [options] file
irrecord: invalid argument count

I copied a file
cp /usr/share/lirc-remotes/samsung/BN59-00516A /etc/lirc/lircd.conf

->nothing better

I launched IRKick (KDE IR interface) : ->no available device. You should
configure one

I tried to configure xirw : ->

checking for strtoul... yes
checking for lirc_init in -llirc_client... no
checking how to run the C++ preprocessor... c++ -E
checking for main in -lFestival... no
configure: error: *** LIRC client support not available ***

What is missing to get a proper LIRC system ?

My Laptop is an IBM T42.
I don't know how to detect which IR is inside.

Many thanks

gd

------------------------------------------------------------------------------

Christoph Bartelmus | 3 May 20:58 2010
Picon

Re: lirc_dev: generic implementation of LIRC_{GET|SET}_SEND_MODE V2

Hi Maxim,

on 02 May 10 at 16:08, Maxim Levitsky wrote:
[...]
>> I'd add a printk here that this ioctl is obsolete and also mark it
>> obsolete in lirc.h.
[...]
>>> +	case LIRC_SET_SEND_MODE:
>>
>> Also mark this obsolete.
> I think I put all obsolete ioctls to the end, after the line 'obsolete'
> Which ones I missed?

What I ment is to also add a printk here as well.

If you think you have all bits ready, just go ahead and put it into CVS.

Christoph

------------------------------------------------------------------------------

Marc MERLIN | 5 May 19:18 2010

lirc 0.8.6's lirc_i2c doesn't work (2.6.33.2 or ubuntu's 2.6.32-21)

I've had lircd work fine on my mythtv for years.

I had to upgrade lirc and kernels because ubuntu lucid forced me (devtmpfs
requirement for it to even boot, pretty sad if you ask me).

Anyway, I upgraded 

myth:~# modprobe lirc_i2c
cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
lirc_i2c: chip 0x0 found  <at>  0x18 (Leadtek IR)
lirc_dev: lirc_register_driver: sample_rate: 10
svc: failed to register lockdv1 RPC service (errno 97).
myth:~# lircd -n -d /dev/lirc1 &
myth:~# lircd-0.8.6[6594]: lircd(default) ready, using /var/run/lirc/lircd
myth:~# irw &
[2] 6629
myth:~# lircd-0.8.6[6628]: accepted new client on /var/run/lirc/lircd

Sending remote control commands displays nothing in irw, and strace on lircd
shows lircd isn't receiving anything from /dev/lirc1 which I know is the
right device (it was created by modprobe lirc_i2c)

I also have a /dev/lirc0 which does trigger reads on lircd when run to read that device,
that's the volume button on my mythtv case:
lirc_dev: IR Remote Control driver registered, major 61 
lirc_imon: Driver for SoundGraph iMON MultiMedia IR/Display, v0.6
lirc_dev: lirc_register_driver: sample_rate: 0
lirc_imon: Registered iMON driver (lirc minor: 0)
lirc_imon: iMON device (15c2:ffdc, intf0) on usb<6:2> initialized
usbcore: registered new interface driver lirc_imon
lirc_imon: IR port opened
lirc_imon: IR port closed

So lirc 0.8.6 isn't totally busted but lirc_i2c doesn't see anything from my 
PVR-500 that's been working fine for years.

Any ideas?

Thanks,
Marc
--

-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

------------------------------------------------------------------------------

Marc MERLIN | 5 May 19:34 2010

lirc 0.8.6's lirc_i2c doesn't work (2.6.33.2 or ubuntu's 2.6.32-21)

I've had lircd work fine on my mythtv for years.

I had to upgrade lirc and kernels because ubuntu lucid forced me (devtmpfs
requirement for it to even boot, pretty sad if you ask me).

Anyway, I upgraded 

myth:~# modprobe lirc_i2c
cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
lirc_i2c: chip 0x0 found  <at>  0x18 (Leadtek IR)
lirc_dev: lirc_register_driver: sample_rate: 10
svc: failed to register lockdv1 RPC service (errno 97).
myth:~# lircd -n -d /dev/lirc1 &
myth:~# lircd-0.8.6[6594]: lircd(default) ready, using /var/run/lirc/lircd
myth:~# irw &
[2] 6629
myth:~# lircd-0.8.6[6628]: accepted new client on /var/run/lirc/lircd

Sending remote control commands displays nothing in irw, and strace on lircd
shows lircd isn't receiving anything from /dev/lirc1 which I know is the
right device (it was created by modprobe lirc_i2c)

I also have a /dev/lirc0 which does trigger reads on lircd when run to read that device,
that's the volume button on my mythtv case:
lirc_dev: IR Remote Control driver registered, major 61 
lirc_imon: Driver for SoundGraph iMON MultiMedia IR/Display, v0.6
lirc_dev: lirc_register_driver: sample_rate: 0
lirc_imon: Registered iMON driver (lirc minor: 0)
lirc_imon: iMON device (15c2:ffdc, intf0) on usb<6:2> initialized
usbcore: registered new interface driver lirc_imon
lirc_imon: IR port opened
lirc_imon: IR port closed

So lirc 0.8.6 isn't totally busted but lirc_i2c doesn't see anything from my 
PVR-500 that's been working fine for years.

Any ideas?

Thanks,
Marc
--

-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

------------------------------------------------------------------------------

Jarod Wilson | 5 May 22:34 2010

Re: lirc 0.8.6's lirc_i2c doesn't work (2.6.33.2 or ubuntu's 2.6.32-21)

On Wed, May 5, 2010 at 1:18 PM, Marc MERLIN <marc@...> wrote:
> I've had lircd work fine on my mythtv for years.
>
> I had to upgrade lirc and kernels because ubuntu lucid forced me (devtmpfs
> requirement for it to even boot, pretty sad if you ask me).
>
> Anyway, I upgraded
>
> myth:~# modprobe lirc_i2c
> cx88/0: cx2388x v4l2 driver version 0.0.7 loaded
> lirc_i2c: chip 0x0 found  <at>  0x18 (Leadtek IR)
> lirc_dev: lirc_register_driver: sample_rate: 10
> svc: failed to register lockdv1 RPC service (errno 97).
> myth:~# lircd -n -d /dev/lirc1 &
> myth:~# lircd-0.8.6[6594]: lircd(default) ready, using /var/run/lirc/lircd
> myth:~# irw &
> [2] 6629
> myth:~# lircd-0.8.6[6628]: accepted new client on /var/run/lirc/lircd
>
>
> Sending remote control commands displays nothing in irw, and strace on lircd
> shows lircd isn't receiving anything from /dev/lirc1 which I know is the
> right device (it was created by modprobe lirc_i2c)
>
> I also have a /dev/lirc0 which does trigger reads on lircd when run to read that device,
> that's the volume button on my mythtv case:
> lirc_dev: IR Remote Control driver registered, major 61
> lirc_imon: Driver for SoundGraph iMON MultiMedia IR/Display, v0.6
> lirc_dev: lirc_register_driver: sample_rate: 0
> lirc_imon: Registered iMON driver (lirc minor: 0)
> lirc_imon: iMON device (15c2:ffdc, intf0) on usb<6:2> initialized
> usbcore: registered new interface driver lirc_imon
> lirc_imon: IR port opened
> lirc_imon: IR port closed
>
>
> So lirc 0.8.6 isn't totally busted but lirc_i2c doesn't see anything from my
> PVR-500 that's been working fine for years.
>
> Any ideas?

Ubuntu fail. I fixed that problem way back in December. Use lirc_i2c
from lirc cvs and it should work fine.

--

-- 
Jarod Wilson
jarod@...

------------------------------------------------------------------------------

Kumar kappera | 6 May 12:05 2010
Picon

Personal invitation from Kumar kappera

If you are not able to click these links, click the following: « Show content » and try again.
E-mail sent 5/6/2010 6:05:03 AM, by Kumar kappera:
Personal invitation from Kumar kappera

Hello,

Finally, a smart and simple way to manage your contacts!

With UNYK, I put all my contacts together in one address book that is automatically updated. One of my contacts changes his or her information at UNYK.com: My address book is updated. I change information at UNYK.com: My contacts’ address books are updated. Simple, but life-changing!

Can I add you as one of my contacts? To accept, click here!

You too can create your own smart address book.

Kumar kappera
UNYK : VZH 168
See who else has invited you to UNYK:
UNYK, the first smart address book that updates itself!
Please do not reply to this email directly. Questions? Contact us - http://unyk.com/en/Contact
UNYK Inc., 1010 de Serigny, suite 820, Longueuil, QC, J4K 5G7, Canada.

I no longer wish to receive invitations to join UNYK from Kumar kappera: Unsubscribe

I never again wish to receive invitation to join UNYK: Unsubscribe
------------------------------------------------------------------------------

Gmane