On Tue, Jun 7, 2011 at 8:43 AM, Jarod Wilson <ja...@wilsonet.com> wrote: > On Jun 7, 2011, at 12:31 AM, Dan Christian wrote: > >> Ya, but that's not something an ordinary user knows how to figure out. >> I couldn't find any docs on how to setup devinput, what it is, or >> when to use it. > > http://lirc.org/html/devinput.html
I read that and it didn't make much sense. It doesn't tell me when I would want devinput. The (scarce) advice it gives about what device to use with it was different than what you told me. It tells me how to list possible event devices, but not how to pick which one is right. Most of it is how to debug HAL conflicts and HAL is a (scary) mystery to me (and most users). Also, the lircd documentation (http://www.lirc.org/html/lircd.html) never tells me what are the valid values for --driver (or how to find that if they are dynamic). It has some vague words about dev/input and match strings, but it doesn't make sense to me. Some examples here would be gold. >> It's not at all clear from the documentation how to find and debug >> each of these steps: >> Which driver (the docs say the atilibusb driver is right, not >> ati_remote; > > What docs are you referring to here? Firefly is listed in http://www.lirc.org/html/table.html There is also a devinput listing later on, but it isn't clear when to use that. I saw an entry that matches what I see in front of me and used that. >> but everything has changed in recent kernels). >> What device (I didn't know which directory to look in the device tree, >> which device file to pick, or why). > > See prior link. I read that link and it didn't succeed in answering any of the questions listed. >> What configuration lircd needs for that (hardware.conf setup isn't >> actually documented). > > hardware.conf is a Debian creation that Ubuntu inherited from there. > Upstream lirc has nothing to do with it, so I can't help there. Some documented examples that list every step would help. I looked at the spawned lircd to see exactly what hardware.conf was doing, but I had nothing to compare it to. As I said before, it isn't clear what the possible drivers are, what devices would go with them, or (in the case of devinput) what search strings to use. >> What lircd.conf is needed for the above steps (and why). > > The question of which lircd.conf is covered at that link. The why > is because all devinput devices have keys mapped to the standard > linux input layer key namespace, as defined in include/linux/input.h, > so its impossible for a key to have any other value than the ones > that are defined in that config. True. I never got any output, so I could really determine if it made sense. >> What .lirc/mythtv file (actually, once irw works, this step isn't so hard). >> >> To make it even worse, what are the ir_* drivers that seems to get >> loaded automatically? I couldn't find any info on them. > > 'modinfo <drivername>' is usually a start. You could also ask about > them on the lirc or linux-media mailing lists. I didn't know about modinfo. Now that I know... it doesn't actually give much information. The descriptions are very short and finding/reading the source is beyond my attention span. I don't want to find and join yet another mailing list just to debug a hardware setup. It would be different if this was bleeding edge hardware, but this configuration used to work and now doesn't. Mailing lists are for developers - not users. -Dan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/787735 Title: Snapstream Firefly non-functional -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
