On 15 Feb 2007 05:40:00 +0100, Christoph Bartelmus <[EMAIL PROTECTED]> wrote: > Hi Jon, > > on 14 Feb 07 at 09:44, you wrote: > [...] > > Adding uinput support would also let you get rid of all the X specific > > code since X knows how to read evdev.You just need to do is add a > > small section to your xorg.conf. > > > > Are your interested in adding this support? > > Yes, I like the concept you presented. I can try to implement it in > lircd as soon as I will find some time. > But my todo list is quite long, so don't hold your breath. > > I'm only a bit concerned about scalability. It's easily possible to have > hundreds of remote control definitions in your lircd.conf. Creating a > device node for each of them will be very inefficient.
I have about ten remotes and I thought that was way too many. How can someone live with hundreds? You could only put the remotes you owned into the config file. Or have them all in the config file but don't create the evdev node until the remote is actually used. I'd say only put the ones you care about into the config file or put them all there in a commented out form and enable the ones your want. > [...] > >> I would like to see the kernel drivers being merged into mainline. > >> But don't wait for me doing it. It simply won't happen. > > > If we fix the code up for submission will you test it and maintain the > > drivers in the future? > > I only own a small fraction of the devices supported by LIRC myself. I > could take over one or two drivers, but definitely not all of them. There are sixteen devices drivers in the lirc repo, are maintainers still around for all of them? Getting device drivers into the kernel isn't as hard as you think it is. Just fix up the obvious things like remove support for multiple kernel versions and then post it to some place like usb-devel. The people there will be happy to tell you in great detail what is then wrong with it. It usually takes a part-time effort over a week or two to make everyone happy and you're in. The lirc drivers are tiny compared to some of the other drivers in the kernel. The big problem is if I fix the drivers up without owning the hardware I can't check to make sure they are still functioning. So testers need to be found that own all of the devices. lirc_dev - base driver I'll look at this one and see if I can get it in shape to post this week. What about the rest of these? lirc_atiusb lirc_bt829 lirc_cmdir lirc_gpio lirc_i2c lirc_igorplugusb lirc_imon lirc_it87 lirc_mceusb lirc_mceusb2 - I have this one, that would be my next target lirc_parallel lirc_sasem lirc_serial lirc_sir lirc_streamzap -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
