On Mon, Nov 30, 2009 at 7:24 AM, Mauro Carvalho Chehab <mchehab@xxxxxxxxxx> wrote: > After the boot, a device can open the raw API, disabling any in-kernel > decoding/handling and handle IR directly. Alternatively, an udev rule > can load a different keymap based on some config written on a file. This idea of the in-kernel decoding being disabled when the raw API is opened worries me. What guarantees that the following scenario will not happen? User uses apps which retrieve the decoded IR messages from the kernel. User installs an app which decodes messages via the raw API (not lirc). User's other applications no longer receive IR messages. I know the assumption has been that "only lirc will use the raw API", but this seems like a poor assumption for an API design to me. A related question, what is an application developer who wishes to decode the raw IR signal (for whatever reason) to do? Are they *required* to implement full decoding and feed all the messages back to the kernel so they don't break other applications? For clarity, I'm not arguing for a particular approach, I'm not fully able to follow the discussion on this issue, but this one issue bothered me. Thank you for your time, Kevin > Cheers, > Mauro. > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
