>So, simply changing the check to if (ret<0) seems to resolve this.  Then if 
>-ENOMEM is returned it will fail, and otherwise succeed.

>Sorry, this is not an official patch.  The maintainer (Jarod?) should be able 
>to see what I am talking about and correct this.

>Thanks!

Last email on this topic for awhile.

The module loads, but there is definitely an issue beyond me at this point.
The second zilog device detected not sending, even though it looks good:

[ 3247.366917] lirc_zilog: Zilog/Hauppauge IR driver initializing
[ 3247.369339] lirc_zilog: probing IR Rx on Hauppage HD PVR I2C (i2c-1)
[ 3247.369346] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C (i2c-1) done. 
Waiting on IR Tx.
[ 3247.369352] lirc_zilog: probing IR Tx on Hauppage HD PVR I2C (i2c-1)
[ 3247.369477] i2c i2c-1: lirc_dev: driver lirc_zilog registered at minor = 1
[ 3247.622652] lirc_zilog: Zilog/Hauppauge IR blaster firmware version 2.1.0 
loaded
[ 3247.622657] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C (i2c-1) done. 
IR unit ready.
[ 3247.622671] lirc_zilog: probing IR Rx on Hauppage HD PVR I2C (i2c-2)
[ 3247.622675] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C (i2c-2) done. 
Waiting on IR Tx.
[ 3247.622680] lirc_zilog: probing IR Tx on Hauppage HD PVR I2C (i2c-2)
[ 3247.622835] i2c i2c-2: lirc_dev: driver lirc_zilog registered at minor = 2
[ 3247.869401] lirc_zilog: Zilog/Hauppauge IR blaster firmware version 2.1.0 
loaded
[ 3247.869406] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C (i2c-2) done. 
IR unit ready.
[ 3247.869446] lirc_zilog: initialization complete


However:
root@jgauthier-mythtv:# irsend -d/var/run/lirc/hdpvr0 SEND_ONCE blaster 
0_74_KEY_2
root@jgauthier-mythtv:# irsend -d/var/run/lirc/hdpvr1 SEND_ONCE blaster 
0_74_KEY_2
irsend: command failed: SEND_ONCE blaster 0_74_KEY_2
irsend: hardware does not support sending


First one worked. Second does not.  

Thanks,

Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to