[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200809111509.51901.jwilson@redhat.com>
Date: Thu, 11 Sep 2008 15:09:51 -0400
From: Jarod Wilson <jwilson@...hat.com>
To: Christoph Bartelmus <lirc@...telmus.de>
Cc: j@...nau.net, linux-kernel@...r.kernel.org, lkml@...breakpoint.cc,
superm1@...ntu.com
Subject: Re: [PATCH 01/18] lirc core device driver infrastructure
On Thursday 11 September 2008 14:30:00 Christoph Bartelmus wrote:
> Hi,
>
> on 09 Sep 08 at 13:03, Jarod Wilson wrote:
> > On Tuesday 09 September 2008 03:40:18 Sebastian Siewior wrote:
>
> [...]
>
> >>>+EXTRA_CFLAGS =-DIRCTL_DEV_MAJOR=61 -DLIRC_SERIAL_TRANSMITTER -I$(src)
> >>
> >> Do you rely on this specific major? Since your daemon opens /dev/lirc0
> >> you don't need a fixed major do you?
> >
> > Good question. Quite honestly, I'm not sure. Christoph?
>
> LIRC does not rely on a specific major. But to be honest, the last time I
> looked into this issue, was when devfs was bleeding-edge...
>
> So, we need some advice here how to proceed. Should we try to register an
> official major number for LIRC? Should we try to have a minor number
> mapping, e.g.
> /dev/lirc/serial/0 LIRC device on 1st UART serial port
> ...
> /dev/lirc/serial/n LIRC device on n-th UART serial port
> /dev/lirc/parallel/0 LIRC device on 1st parallel port
> ...
> /dev/lirc/parallel/n LIRC device on n-th parallel port
> /dev/lirc/usb/0 1st LIRC USB device
> ...
Janne took a crack at dynamic device allocation earlier today, committed into
my git tree:
http://git.wilsonet.com/linux-2.6-
lirc.git/?a=commitdiff;h=ea74897bf7b03e2ed2401df3815637caa0702eab
Haven't yet tested it out, that's on tap for tonight...
--
Jarod Wilson
jarod@...hat.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists