>> The rc-core register (and the corresponding input register) is done when>> the device detected a remote controller, so, it should be safe to register>> on that point. If not, IMHO, there's a bug somewhere. > > It is not a matter of safe or unsafe registration. Registration is fine.> The problem is that with the current set up is that utility is fired> when trunk of [sub]tree is created, but the utility wants to operate on> leaves which may not be there yet.

I'm not an udev expert. Is there a udev event that hits only after havingthe driver completely loaded? Starting an udev rule while modprobe isstill running is asking for race conditions.

I'm not entirely convinced that this is the bug that Mark is hitting, asrc-core does all needed setups before registering the evdev device. Weneed the core and the dmesg to be sure about what's happening there.

>> Yet, I agree that udev tries to set devices too fast.> > It tries to set devices exacty when you tell it to do so. It's not like> it goes trolling for random devices is sysfs.> >> It would be better if>> it would wait for a few milisseconds, to reduce the risk of race conditions.> > Gah, I really prefer using properly engineered solutions instead of> adding crutches.

I agree.

>>> And this could be easily added to the udev's keymap utility that is>>> fired up when we discover evdevX devices.>>>> Yes, it can, if you add the IR protocol selection on that tool. A remote >> controller keycode table has both the protocol and the keycodes.>> This basically means to merge 99% of the logic inside ir-keytable into the>> evdev generic tool.> > Or just have an utility producing keymap name and feed it as input to> the generic tools. The way most of utilities work...

I don't like the idea of running a some logic at udev that would generatesuch keymap in runtime just before calling the generic tool. The otheralternative (e. g.) to maintain the RC-protocol dependent keytables separatefrom the RC protocol used by each table will be a maintenance nightmare.

>>>> Also, I'm currently working on a way to map media keys for remote controllers >>>> into X11 (basically, mapping them into the keyspace between 8-255, passing >>>> through Xorg evdev.c, and then mapping back into some X11 symbols). This way,>>>> we don't need to violate the X11 protocol. (Yeah, I know this is hacky, but>>>> while X11 cannot pass the full evdev keycode, at least the Remote Controllers>>>> will work). This probably means that we may need to add some DBus logic>>>> inside ir-keytable, when called via udev, to allow it to announce to X11.>>>>>> The same issue is present with other types of input devices (multimedia>>> keyboards emitting codes that X can't consume) and so it again would>>> make sense to enhance udev's utility instead of confining it all to>>> ir-keytable.>>>> I agree with you, but I'm not sure if we can find a solution that will>> work for both RC and media keyboards, as X11 evdev just maps keyboards>> on the 8-255 range. I was thinking to add a detection there for RC, and>> use a separate map for them, as RC don't need most of the normal keyboard>> keys.> > Well, there will always be clashes - there is reason why evdev goes> beyond 255 keycodes...

Yeah. The most appropriate fix would be for X to just use the full evdevkeycode range. However, I'm not seeing any indication that such changewill happen soon. Not sure if there are some news about it at LCA, asthere were one speech about this subject there.