From: Robert Read <rread@datarithm.net>
To: Ari Pollak <compwiz@datarithm.net>, linux-kernel@vger.kernel.org
Subject: Re: devices.txt inconsistency
Date: Mon, 1 Jan 2001 23:24:54 +0000 [thread overview]
Message-ID: <20010101232454.C8481@tenchi.datarithm.net> (raw)
In-Reply-To: <20010101170654.A5856@sourceware.net>
In-Reply-To: <20010101170654.A5856@sourceware.net>; from compwiz@bigfoot.com on Mon, Jan 01, 2001 at 05:06:54PM -0500
devices.txt does need some updating. It still lists char-major-13 as
the PC Speaker, but 13 appears to be the major for new input driver,
and the joystick driver is now a minor off the that. Are there now
two Joystick drivers, or can char-major-15 be obsoleted/deleted?
robert
On Mon, Jan 01, 2001 at 05:06:54PM -0500, Ari Pollak wrote:
> This has not been fixed for at least a year that i can remember - in
> Documentation/devices.txt, it says /dev/js* should be char-major-15*,
> but in Documentation/joystick.txt it says it should be char-major-13.
> I'm assuming joystick.txt is the correct one, and devices.txt should be
> updated to reflect this.. before 2.4.0 would be nice.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-01 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 22:06 devices.txt inconsistency Ari Pollak
2001-01-01 23:24 ` Robert Read [this message]
2001-01-01 23:48 ` H. Peter Anvin
2001-01-02 13:37 ` ratz
2001-01-01 23:35 ` Robert Read
-- strict thread matches above, loose matches on Subject: below --
2001-01-02 16:19 Douglas Gilbert
2001-01-02 17:29 ` H. Peter Anvin
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=20010101232454.C8481@tenchi.datarithm.net \
--to=rread@datarithm.net \
--cc=compwiz@datarithm.net \
--cc=linux-kernel@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