LIRC has been disabled in the latest patch to linux-ubuntu-modules. It
wasn't functional for the users that needed it, and was loading for the
users who didn't Instead, users will have to use /dev/input for GPIO
devices, unless this gets fixed upstream with a buildable, functional
GPIO module on
Done.
--
Lirc GPIO module not buildable on 2.6.22 kernel
https://bugs.launchpad.net/bugs/125384
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
Daniel,
At this moment, things are being re-evaluated. Could you remove
ubuntu-main-sponsors from this bug? I'll have a newer lirc patch after this
is determined upstream.
Mario
On 8/22/07, Daniel Holbach <[EMAIL PROTECTED]> wrote:
>
> Which patch should be sponsored at the moment?
>
> --
> Li
Which patch should be sponsored at the moment?
--
Lirc GPIO module not buildable on 2.6.22 kernel
https://bugs.launchpad.net/bugs/125384
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
> Adapting this to work in a plug and play fashion however, that is
another story :)
I think the only needed lines on most configurations are:
alias char-major-81 videodev
alias char-major-81-0 bttv
Adding this to default modprobe options on all systems shouldn't be so
traumatic, as well as an u
yS,
This is a quite valuable find here for a solution. I'm going to query
lirc-list to see if they would be willing to deprecate the usage of the
module in modern kernels. I think for now that lirc_gpio driver will
need to be removed from the build. Adapting this to work in a plug and
play fash
It seems we don't need lirc_gpio anymore.
I've followed the steps found at
http://bugs.archlinux.org/task/7660?pagenum=11 and
http://www.sthoughts.com/?p=332 to make it working. However, we should
find a plug-and-go solution to this.
First, unload lirc_dev, lirc_gpio, bttv. Then create this file:
Same here.
Here's a lirc typical die:
# lircd -n
lircd-0.8.2[21492]: lircd(userspace) ready
lircd-0.8.2[21492]: accepted new client on /dev/lircd <-- kde
tries to connect
lircd-0.8.2[21492]: could not get file information for /dev/lirc
lircd-0.8.2[21492]: default_init(): No such fi
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Status: Fix Committed => Confirmed
--
Lirc GPIO module not buildable on 2.6.22 kernel
https://bugs.launchpad.net/bugs/125384
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Before (with 2.6.22-8 and my modifications in the kernel source) it was:
$ lsmod | grep lirc
lirc_gpio 11184 1
lirc_dev 16116 1 lirc_gpio
bttv 172788 2 lirc_gpio,bt878
$ lsmod | grep bttv
bttv 172788 2 lirc_gpio,bt878
video_buf
I installed the package.
Now lirc_gpio can be loaded, and lircd launched... but when I run irw, lircd
dies.
Something strange I noticed is that lirc_gpio doesn't depend on bttv as it used
to do:
# lsmod | grep lirc
lirc_gpio 37088 0
lirc_dev 15860 0
# lsmod | gre
It will be seen in this release:
linux-ubuntu-modules-2.6.22 (2.6.22-9.21) gutsy; urgency=low
[Ben Collins]
* ABI bump
* rt2x00: Update from wireless-dev, v2.0.4
* ubuntu: Add -rt for i386/amd64 builds
[Mario Limonciello]
* lirc: Fix support for Hauppauge I2C devices
* lirc: Add
Mario, when you've got the workaround, post here the module lirc_gpio.ko
(compiled for 2.6.22-8-generic). I'll write it to /lib/modules/ and try
to load it. If it does, I'll test it with "irw" command.
If all of that works, then I'll make the final test by undoing the
changes to bttv I did and tes
Do you reffer on something that uses that module? Only lirc itself...
I currently have it working with my patched bttv and standard lirc_gpio
(compiled from source as I recommended in my howto)
--
Lirc GPIO module not buildable on 2.6.22 kernel
https://bugs.launchpad.net/bugs/125384
You received
As this only affects lirc_gpio, i don't think using the deprecated functions
outside of lirc_gpio would be a good idea (putting this patch back out to
the kernel sources). I've already got work arounds in the source to include
missing bttv headers there. I'll see what happens. Hexion do you have
Is that possible? Lost functions are provided by an external module
(bttv), so if you want to implement those functions inside lirc_gpio, it
should have access to the internal implementation of bttv. And that
would require to export all the variables and functions that those 2
functions use, to be
As a temporary workaround, those functions (and headers) might suffice in
the lirc_gpio source directly rather than modifying the kernel sources.
I'll do some experiments, and if things appear to work correctly push the
changes back out to linux-ubuntu-modules. Otherwise, we'll have to wait for
a
I think you didn't understand...
Well, this is a problem with lirc, but it's because linux developers
have dropped some functions from the BTTV module. There's a new API to
be used, but lirc developers haven't change the code to adapt it.
It's unlikely that they fix it before Gutsy is released (a
The headers aren't available because they aren't in the normal place
(include/). We build lirc modules in linux-ubuntu-modules. If any are
missing, file a bug there and we can see about getting that worked out
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Invalid
--
Lirc GPIO
To build lirc_gpio, we need to hack the kernel until lirc devs solve the
problem
** Changed in: linux-source-2.6.22 (Ubuntu)
Sourcepackagename: lirc => linux-source-2.6.22
Status: Confirmed => New
--
Lirc GPIO module not buildable on 2.6.22 kernel
https://bugs.launchpad.net/bugs/125384
Yo
** Attachment added: "bttv-if.c"
http://launchpadlibrarian.net/8561247/bttv-if.c
--
Lirc GPIO module not buildable on 2.6.22 kernel
https://bugs.launchpad.net/bugs/125384
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubun
After reading posts in the mailing list of Lirc, and the bug you filed
in launchpad, I started thinking about how to solve this problem.
Well, I got it Now I'm running Lirc with 2.6.22 kernel using lirc_gpio
module.
I simply added the functions droped in the source code, recompiled some
modules,
Sorry, I misunderstood what this patch was for...
After reading some posts in the Lirc mailing list (included yours), I
realized that there's no solution yet since some symbols have been
deleted in the vanilla kernel. I suppose this patch is then to make
lirc_gpio build, it's not intended to make
It's still not buildable here.
I followed your instructions here:
https://help.ubuntu.com/community/Install_Lirc_Feisty
but with no results:
# modprobe lirc_gpio
FATAL: Error inserting lirc_gpio
(/lib/modules/2.6.22-8-generic/misc/lirc_gpio.ko): Unknown symbol in module, or
unknown parameter (se
lirc (0.8.2-0ubuntu2) gutsy; urgency=low
* Make sure lirc_gpio is buildable by adding extra_2.6.22
to 03_extra_files.dpatch. (LP: #125384)
* Add 05_fix_cmdir.dpatch from lirc CVS to fix cmdir linking
issues.
* Add a symbolic link in case /usr/share/doc/lirc/lirc.hwdb
is being use
** Changed in: lirc (Ubuntu)
Status: In Progress => Confirmed
--
Lirc GPIO module not buildable on 2.6.22 kernel
https://bugs.launchpad.net/bugs/125384
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
The attached debdiff fixes compilation of lirc-modules-source's gpio
module. Also, this resolves issues with cmdir linking that were later
discovered.
** Attachment added: "debdiff fixing gpio and cmdir"
http://launchpadlibrarian.net/8452664/lirc-ubuntu1-ubuntu2.debdiff
--
Lirc GPIO module n
27 matches
Mail list logo
