On Mon, 01 Oct 2007, Andrew Sackville-West wrote:
> On Mon, Oct 01, 2007 at 12:04:28AM -0400, Brad Sawatzky wrote:
> > On Sat, 29 Sep 2007, Greg Vickers wrote:
> >
> > > OK, I found out that Debian Etch uses a new input layer, and that the IR
> > > inputs are in /dev/input/eventX where X corresp
On Mon, Oct 01, 2007 at 12:04:28AM -0400, Brad Sawatzky wrote:
> On Sat, 29 Sep 2007, Greg Vickers wrote:
>
> > OK, I found out that Debian Etch uses a new input layer, and that the IR
> > inputs are in /dev/input/eventX where X corresponds the event number of
> > your input devices in 'cat /pro
On Sat, 29 Sep 2007, Greg Vickers wrote:
> OK, I found out that Debian Etch uses a new input layer, and that the IR
> inputs are in /dev/input/eventX where X corresponds the event number of
> your input devices in 'cat /proc/bus/input/devices'
>
> So my IR device is /dev/input/event1, instead of
Hi all,
Marty wrote:
Greg Vickers wrote:
Hi Marty,
Sorry. I'm not familiar with udev or lirc, nor how they interact in
deciding device names. It's surprising to me because I'm using the
upstream lirc, 0.8.2, and I get /dev/lirc0, as Debian's udev expects.
I'll try my mitigation stra
Greg Vickers wrote:
Hi Marty,
Marty wrote:
David Brodbeck wrote:
I find with LIRC it's usually easiest to abandon using packages and
build it from scratch. It seems to be much easier to configure that
way. I realize this isn't the Debian-correct(tm) way to do it but
it's usually what I
Hi Marty,
Marty wrote:
David Brodbeck wrote:
I find with LIRC it's usually easiest to abandon using packages and
build it from scratch. It seems to be much easier to configure that
way. I realize this isn't the Debian-correct(tm) way to do it but
it's usually what I resort to.
In the c
David Brodbeck wrote:
I find with LIRC it's usually easiest to abandon using packages and
build it from scratch. It seems to be much easier to configure that
way. I realize this isn't the Debian-correct(tm) way to do it but
it's usually what I resort to.
In the case or the original poste
I find with LIRC it's usually easiest to abandon using packages and
build it from scratch. It seems to be much easier to configure that
way. I realize this isn't the Debian-correct(tm) way to do it but
it's usually what I resort to.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
Greg Vickers wrote:
Hi Andrew,
Andrew Sackville-West wrote:
On Sun, Sep 23, 2007 at 05:14:36PM +1000, Greg Vickers wrote:
Hi all,
I'm trying to get lirc to work with my Hauppauge on my Debian installation
on AMD64. I've used module assistant to create the lirc kernel modules and
the module
Hi Andrew,
Andrew Sackville-West wrote:
On Sun, Sep 23, 2007 at 05:14:36PM +1000, Greg Vickers wrote:
Hi all,
I'm trying to get lirc to work with my Hauppauge on my Debian installation
on AMD64. I've used module assistant to create the lirc kernel modules and
the modules install and modprob
Greg Vickers wrote:
Hi Marty,
Marty wrote:
Greg Vickers wrote:
Hi all,
I'm trying to get lirc to work with my Hauppauge on my Debian
installation on AMD64. I've used module assistant to create the lirc
kernel modules and the modules install and modprobe successfully:
# lsmod | grep lirc
l
Hi Marty,
Marty wrote:
Greg Vickers wrote:
Hi all,
I'm trying to get lirc to work with my Hauppauge on my Debian
installation on AMD64. I've used module assistant to create the lirc
kernel modules and the modules install and modprobe successfully:
# lsmod | grep lirc
lirc_i2c
On Sun, Sep 23, 2007 at 05:14:36PM +1000, Greg Vickers wrote:
> Hi all,
>
> I'm trying to get lirc to work with my Hauppauge on my Debian installation
> on AMD64. I've used module assistant to create the lirc kernel modules and
> the modules install and modprobe successfully:
> # lsmod | grep li
Greg Vickers wrote:
Hi all,
I'm trying to get lirc to work with my Hauppauge on my Debian
installation on AMD64. I've used module assistant to create the lirc
kernel modules and the modules install and modprobe successfully:
# lsmod | grep lirc
lirc_i2c 14980 0
lirc_dev
14 matches
Mail list logo
