From: Todd Musall <tmusall@comcast.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev 024 and LIRC support
Date: Wed, 14 Apr 2004 19:52:34 +0000 [thread overview]
Message-ID: <1081972354.14688.9.camel@parents> (raw)
Greg,
Good question. I've been waiting a long time for the merge. I'm using
the patch from:
http://flameeyes.web.ctonet.it/lirc/
lirc-2.6.4-20040318.bz2
I had to modify Kconfig slightly before it would apply, but it does
work.
Here's my Kconfig patch:
--- lirc-2.6.4-20040318 2004-04-06 18:35:46.000000000 -0400
+++ lirc-2.6.4-20040318.new 2004-04-06 18:43:15.000000000 -0400
@@ -56,18 +56,17 @@ diff -Npaur linux-2.6.4/Documentation/li
+
+1. enabling/using shared IRQ
+2. init/drop IRQ-usage in lirc_open/lirc_close
-diff -Npaur linux-2.6.4/drivers/char/Kconfig
linux-2.6.4-lirc/drivers/char/Kconfig
---- linux-2.6.4/drivers/char/Kconfig 2004-03-15 14:44:47.533164736
+0100
-+++ linux-2.6.4-lirc/drivers/char/Kconfig 2004-03-15 15:03:14.207924600
+0100
-@@ -600,6 +600,8 @@ config PC9800_OLDLP_CONSOLE
- depends on PC9800_OLDLP
+--- linux-2.6.5/drivers/Kconfig 2004-04-03 22:38:17.000000000 -0500
++++ linux-2.6.5/drivers/Kconfig.new 2004-04-06 18:35:02.000000000 -0400
+@@ -42,6 +42,8 @@ source "drivers/char/Kconfig"
+ source "drivers/i2c/Kconfig"
+source "drivers/char/lirc/Kconfig"
+
- menu "Mice"
+ source "drivers/misc/Kconfig"
- config BUSMOUSE
+ source "drivers/media/Kconfig"
diff -Npaur linux-2.6.4/drivers/char/Kconfig.orig
linux-2.6.4-lirc/drivers/char/Kconfig.orig
--- linux-2.6.4/drivers/char/Kconfig.orig 1970-01-01 01:00:00.000000000
+0100
+++ linux-2.6.4-lirc/drivers/char/Kconfig.orig 2004-03-15
14:44:47.533164736 +0100
-Todd
On Wed, 2004-04-14 at 15:13, Greg KH wrote:
> On Mon, Apr 12, 2004 at 11:26:15PM -0400, Todd Musall wrote:
> > Greg,
> >
> > Instead I used this rule to create /dev/vc/[0-9] symlinks:
> >
> > KERNEL="tty[0-9]", NAME="%k", SYMLINK="vc/%m"
> >
> > Works like a charm.
> >
> > I've almost got udev completely working. My last issue is with LIRC.
> > The device node /dev/lirc0 isn't being created. I'm using a patched
> > LIRC version for 2.6 kernels and on devfs everything works fine. I
> > haven't had time to debug it further but wondered if anyone else has got
> > LIRC working with udev?
>
> Odds are lirc code needs to be patched to work with sysfs. Does anyone
> know why the lirc code is not in the mainline kernel? I can't seem to
> be able to connect to the site that holds their 2.6 kernel patch...
>
> greg k-h
--
Todd Musall <tmusall@comcast.net>
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2004-04-14 19:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1081972354.14688.9.camel@parents \
--to=tmusall@comcast.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).