Re: Patch: Fix typo in lirc.hwdb for dev/input

[Mario L. <mar...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christoph Bartelmus wrote:
> Hi!
> 
> Mario Limonciello "mar...@gm..." wrote:
> [...]
>> I've got a patch to include from the Ubuntu packages that corrects a typo in
>> the lirc.hwdb file preventing proper automation when parsing the file.
> 
> lirc.hwdb is a generated file, so please don't edit it.
> I've fixed the missing commandir module. The devinput bug is fixed in  
> CVS already.
> 
> Concerning the newly supported devices: those should be added to  
> setup.data.
> 
> Concerning config files for devinput devices: I don't see any point  
> saving them for all kinds of devices as there should be one generic file  
> only, like e.g.
> http://linux.bytesex.org/v4l2/faq.html#lircd
> http://linux.bytesex.org/v4l2/linux-input-layer-lircd.conf
> 
> Christoph
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
Christoph,

Thanks for the information here.  I wasn't particularly sure how lirc.hwdb was
actually generated.  When you say automatically generated, I haven't seen it
changed during package building.  Is it automatically generated on your end at
some point, or is this a bug?

I guess there are two philosophies here upon what items should be listed in the
lirc.hwdb file.  It all boils down to how you use it though.

The first method would be by driver.  You know that your device uses the
dev/input driver by nothin more.  This is really convenient if you know a lot
about your device already.

The second method is by the remote.  I think this is the most useful way to look
at it.  Someone knowing nothing about LIRC, but wanting to use it would be able
to get involved quicker.  I see your point about the common configuration file,
and will update our patchset in the next upload to make sure all remotes using
dev/iput use that same file instead.  I still do think its better to break out
the remotes here however rather than grouping them into 2 or more items.  What
Ubuntu is doing right now is parsing this file upon package installation.  The
user is presented a debconf dialog that they can look through that parsed list
and choose their remote.  We then copy the remote referenced as the last field
in each line to the systemwide lircd.conf and configure hardware.conf (which is
used by the debian & Ubuntu init script) to load the appropriate modules or at
least use teh right arguments for starting lircd.  In the end this way makes it
really easy for the user to get going.

  Any idea whether or not this common lircd configuration will be working for
GPIO devices (since GPIO is still broken in 2.6.22) using the method to
configure GPIO devices using dev/input to the list a bit ago?

Regards,

- --
Mario Limonciello
mar...@gm...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHKb3KTIvEyIDfbVgRAqJ7AJ45jKBbZhjnRLVs9W0Ukpz1dfXn6wCgmXev
avybLGZxrGlaZWQJXIFUYrg=
=cw/K
-----END PGP SIGNATURE-----