public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Read <rread@datarithm.net>
To: linux-kernel@vger.kernel.org
Subject: Re: devices.txt inconsistency
Date: Mon, 1 Jan 2001 23:35:20 +0000	[thread overview]
Message-ID: <20010101233520.D8481@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

How's this?  Should char-major-15 be obsoleted, deleted or just left
in for now?

robert

--- linux/Documentation/devices.txt.bak Mon Jan  1 15:29:24 2001
+++ linux/Documentation/devices.txt     Mon Jan  1 15:33:38 2001
@@ -430,14 +430,14 @@
                  1 = /dev/dos_cd1      Second MSCDEX CD-ROM
                    ...
 
- 13 char       PC speaker (OBSOLETE)
-                 0 = /dev/pcmixer      Emulates /dev/mixer
-                 1 = /dev/pcsp         Emulates /dev/dsp (8-bit)
-                 4 = /dev/pcaudio      Emulates /dev/audio
-                 5 = /dev/pcsp16       Emulates /dev/dsp (16-bit)
+ 13 char       Generic Input Driver
+                 0  = /dev/input/js0        First joystick
+                 1  = /dev/input/js1        Second joystick
+                    ...
 
-               The current PC speaker driver uses the Open Sound
-               System interface, and these devices are obsolete.
+                 64 = /dev/input/event0     For testing/debugging
+                 65 = /dev/input/event1
+                   ...
 
     block      8-bit MFM/RLL/IDE controller
                  0 = /dev/xda          First XT disk whole disk                        

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/

  parent reply	other threads:[~2001-01-01 23:46 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
2001-01-01 23:48   ` H. Peter Anvin
2001-01-02 13:37     ` ratz
2001-01-01 23:35 ` Robert Read [this message]
  -- 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=20010101233520.D8481@tenchi.datarithm.net \
    --to=rread@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