From: Flameeyes <dgp85@users.sourceforge.net>
To: LKML <linux-kernel@vger.kernel.org>,
LIRC list <lirc-list@lists.sourceforge.net>
Subject: [PATCH] Lirc Drivers for 2.5/6 20030806 [devfs enabled]
Date: 06 Aug 2003 17:06:34 +0200 [thread overview]
Message-ID: <1060182394.7828.8.camel@defiant.flameeyes> (raw)
This is the fifth try for the lirc patch, and fixes a big problem, the
missing of devfs suppor in the previous patches.
Download it from here
http://flameeyes.is-a-geek.org/lirc/patch-lirc-20030806.diff.bz2 .
I have switched to gentoo this week (after a rootfs failure on my debian
box), so the devfs suport was the priority.
I also merged another change to lirc_dev from lirc cvs.
Please note that using devfs you need to provide lircd the path to the
device (-d /dev/lirc/lirc0).
Thanks,
--
Flameeyes <dgp85@users.sf.net>
reply other threads:[~2003-08-06 15:06 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=1060182394.7828.8.camel@defiant.flameeyes \
--to=dgp85@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lirc-list@lists.sourceforge.net \
/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