On Tue, Dec 8, 2009 at 6:17 AM, Mauro Carvalho Chehab <mchehab@xxxxxxxxxx> wrote: > Jon Smirl wrote: >> On Mon, Dec 7, 2009 at 6:44 PM, Mauro Carvalho Chehab >> <mchehab@xxxxxxxxxx> wrote: > >>>> Where is the documentation for the protocol? >>> I'm not sure what you're meaning here. I've started a doc about IR at the media >> >> What is the format of the pulse stream data coming out of the lirc device? > > AFAIK, it is at: > http://www.lirc.org/html/index.html > > It would be nice to to add it to DocBook after integrating the API in kernel. > The point of those design review questions was to illustrate that the existing LIRC system is only partially designed. Subsystems need to be fully designed before they get merged. For example 36-40K and 56K IR signals are both in use. It is a simple matter to design a receiver (or buy two receivers) that would support both these frequencies. But the current LIRC model only supports a single IR receiver. Adjusting it to support two receivers is going to break the ABI. My choice would be to just tell the person with the 56K remote to just buy a new 38K remote, but other people are against that choice. That forces us into designing a system that can handle multiple receivers. There is a parallel problem with baseband encoded IR signals. We need to think about all of these use cases before designing the ABI. Only after we think we have a good ABI design should code start being merged. Of course we may make mistakes and have to fix the ABI, but there is nothing to be gained by merging the existing ABI if we already know it has problems. -- Jon Smirl jonsmirl@xxxxxxxxx -- 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
