On Mon, Mar 16, 2009 at 05:23:53PM +0200, Antti Palosaari wrote:

Heinrich Langos wrote:

...

On Mon, Mar 16, 2009 at 03:07:21PM +0100, Heinrich Langos wrote:

...

On Mon, Mar 16, 2009 at 02:19:30PM +0200, Antti Palosaari wrote:

...

remote=0 does not disable polling, it is for selecting correct remote.

Well, setting remote=0 does have an effect (af9015.c):

            if (val == AF9015_IR_MODE_DISABLED || val == 0x04) {
                    af9015_properties[i].rc_key_map = NULL;
                    af9015_properties[i].rc_key_map_size  = 0;

val is read from eeprom, there is byte in eeprom which tells whether device have remote or not. If eeprom says no remote then polling is disabled. If you look more carefully there is if-else condition which goes: if (eeprom remote disabled)

• disable remote

else if (module param remote defined)

• load ir-table defined as module param

else

• load ir-table according to USB-ID

You are right. Sorry I didn't read that carefully enough.

I am not sure what happens if device have remote but ir-table is not selected by if-else. Probably .rc_key_map_size leaves to 0 and remote polling is disabled.

Thats exactly what happens. Though, I didn't see a place where af9015_properties[i]rc_key_map is initalized. Maybe a sanity check for the "remote" module parameter should be added? Telling the user that he uses an invalid value could help new users.

Anyhow, this problem is not af9015 specified. Most dvb-usb -drivers have just similar implementation. rc-polling is provided by dvb-usb-core.

Right again. Sorry to bother you.

...

Anyway .. the main problem remains.

Is there a tool that would only do some minimal actions on a dvb device?

Like power_on? femon for example reads device status. zap, scan...

Yeap. Thank you for that list. I'll take a look at those and see what I can find out.

Cheers and thank you very much for your help! -henrik