Dmitry Torokhov wrote: > On Mon, Nov 30, 2009 at 03:33:52PM -0200, Mauro Carvalho Chehab wrote: >> kevin granade wrote: >>> 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. >> All those questions are theoretical, as we haven't a raw API code >> already merged in kernel. So, this is just my understanding on how >> this should work. >> >> If the user wants to use the raw interface, it is because the in-kernel >> decoding is not appropriate for his usage > > Not necessarily, someone might just want to observe the data stream for > one reason or enough. You would not believe how many times I wanted > to use evtest from X but could not because X grabs the device and had > to switch to console.... > >> (at least while such application >> is opened). So, not disabling the evdev output seems senseless. > > You know what they say when you assume things? > >> Btw, this is the same behavior that happens when some application directly >> opens an evdev interface, instead of letting it to be redirected to stdin. > > Well, console applications don't get their input directly from event > device but even if they did "not redirecting it to stdin" will not > affect any other application that has the same event device open. > > This is a _huge_ difference. > >>> 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? >> If such application won't do it, the IR will stop working, while the >> application is in use. >> > > I don't think it is indication of a good solution. Well, maybe then we may have an ioctl to explicitly disable the evdev processing of the data that could be applied to the raw IR interface, instead of making assumptions. > -- 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
