[ubuntu-mythtv] Mythbuntu - Lirc Ideas

[Mario Limonciello]

Folks,

I have a bit of a follow up regarding the lirc situation, but need some
input what to do now.

I got the new version of lirc (0.8.2) into Gutsy, and a new feature of
it is a nifty lirc.hwdb file.  It outlines what lircd.conf goes with
what remote as well as what driver goes with what remote and some other
info.

The new way the GUI works, is by parsing this file for that information.
 Instantly, all remotes that are supported by LIRC publicly are
supported in mythbuntu.  I've got backend code to sort out using the
correct lircd.conf as well as choosing the right drivers to be loaded.

This leaves two outstanding issues:

1) Anything that needs a kernel module.
Kernel modules need to be recompiled after each kernel release.  We
can't just tell people to keep using the same one over and over.  We
need some possible solutions here how to avoid such a problem.  I Tried
to mail the UMC guys to ask on their progress getting it into the
kernel, but given the no response in the last two days, its probably
better at this point to carry on with alternate solutions.  So bring
them on in.

2) Lircrc config files.
The official lirc website doesn't ship these, but expects the end user
to sort it out instead.  Generating one for each lircd.conf would be an
utter nightmare.  So any ideas how we can do such things on the fly?
It's not exactly a solution to just ship a few of them either.  It's
gotta be all or nothing.

Lastly, see attached files.  This is how the gui is looking for lirc in
the installer.

Mario

Mario Limonciello wrote:
> Hi guys,
> 
> I started the coding for ubiquity yesterday regarding lirc.  I was
> looking for the most ideal way to manage as many remotes as possible.
> 
> The current structure is like this:
> 
> Choose A Remote :		<Common Remotes List>
> 	Choose Driver:		     <Buildable drivers list>
> 	Choose Config:		    <Configuration list>
> 
> The common remotes list includes
> ATI RF, Hauppauge, MS V1, MS V2., Other.
> 
> Choosing a common remote will automatically set the driver and config.
> Choosing other lets you customize the driver and config.
> 
> The drivers list basically has all the possible buildable drivers for
> lirc.  The config list only has configs for those common remotes atm,
> because i'm not sure how to handle much more.
> 
> I'm thinking until the UMC team sorts out including lirc with the kernel
> and such, on mythbuntu.org a repository can be kept that has all the
> possible kernel modules prebuilt for users.  It can update nightly via a
> cron job in case of new kernels.
> 
> Any comments or ideas?
> 
> Mario
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mceusb2.png
Type: image/png
Size: 82609 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/ubuntu-mythtv/attachments/20070711/731c09fe/attachment-0003.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: noremote.png
Type: image/png
Size: 65617 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/ubuntu-mythtv/attachments/20070711/731c09fe/attachment-0004.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: remotelist.png
Type: image/png
Size: 132370 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/ubuntu-mythtv/attachments/20070711/731c09fe/attachment-0005.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-mythtv/attachments/20070711/731c09fe/attachment-0001.pgp