Re: [Fwd: devices.txt inconsistency]
Hi, On Wed, Jan 03, 2001 at 11:01:05AM -0500, Douglas Gilbert wrote: > Stephen, > Did you respond to hpa on this matter? Not yet, I'm just catching up on festive-season email. Happy New Year, all! > [From the cc address it seems as though you > work both for transmeta as well as redhat.] Nope, unless transmeta and red hat have been negotiating behind my back. :) The misdirected email is probably why I didn't spot this earlier. > > but something like this would be more accurate: > > 162 charRaw block device interface > > 0 = /dev/rawctl Raw I/O control device > > 1 = /dev/raw/raw1 First raw I/O device > > 2 = /dev/raw/raw2 Second raw I/O device > > ... > > > > The raw(8) command supplied in RH 6.2 and 7.0 assumes the > > latter structure. I have already alerted sct and this > > change may be coming through in one of his patches. > > The latter is actually better, so I certainly don't mind. sct, should I > change it? Please do: the current util-linux should be using the new layout. Cheers, Stephen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: [Fwd: devices.txt inconsistency]
Hi, On Wed, Jan 03, 2001 at 11:01:05AM -0500, Douglas Gilbert wrote: Stephen, Did you respond to hpa on this matter? Not yet, I'm just catching up on festive-season email. Happy New Year, all! [From the cc address it seems as though you work both for transmeta as well as redhat.] Nope, unless transmeta and red hat have been negotiating behind my back. :) The misdirected email is probably why I didn't spot this earlier. but something like this would be more accurate: 162 charRaw block device interface 0 = /dev/rawctl Raw I/O control device 1 = /dev/raw/raw1 First raw I/O device 2 = /dev/raw/raw2 Second raw I/O device ... The raw(8) command supplied in RH 6.2 and 7.0 assumes the latter structure. I have already alerted sct and this change may be coming through in one of his patches. The latter is actually better, so I certainly don't mind. sct, should I change it? Please do: the current util-linux should be using the new layout. Cheers, Stephen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
Douglas Gilbert wrote: > > While on this subject, the description of raw devices > (char 162) in lk 2.4 is not consistent with current > usage. > > devices.txt contains this: > 162 charRaw block device interface > 0 = /dev/raw Raw I/O control device > 1 = /dev/raw1 First raw I/O device > 2 = /dev/raw2 Second raw I/O device > ... > > but something like this would be more accurate: > 162 charRaw block device interface > 0 = /dev/rawctl Raw I/O control device > 1 = /dev/raw/raw1 First raw I/O device > 2 = /dev/raw/raw2 Second raw I/O device > ... > > The raw(8) command supplied in RH 6.2 and 7.0 assumes the > latter structure. I have already alerted sct and this > change may be coming through in one of his patches. > The latter is actually better, so I certainly don't mind. sct, should I change it? -hpa -- <[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
While on this subject, the description of raw devices (char 162) in lk 2.4 is not consistent with current usage. devices.txt contains this: 162 charRaw block device interface 0 = /dev/raw Raw I/O control device 1 = /dev/raw1 First raw I/O device 2 = /dev/raw2 Second raw I/O device ... but something like this would be more accurate: 162 charRaw block device interface 0 = /dev/rawctl Raw I/O control device 1 = /dev/raw/raw1 First raw I/O device 2 = /dev/raw/raw2 Second raw I/O device ... The raw(8) command supplied in RH 6.2 and 7.0 assumes the latter structure. I have already alerted sct and this change may be coming through in one of his patches. Doug Gilbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
> The current devices.txt is available at: > >http://www.lanana.org/docs/device-list/devices.txt > > I don't have the details for /dev/input/* in there; I need to still > make that update. Small typo fix: --- devices.txt~Tue Jan 2 14:34:32 2001 +++ devices.txt Tue Jan 2 14:34:48 2001 @@ -771,7 +771,7 @@ 36 char Netlink support 0 = /dev/routeRouting, device updates, kernel to user 1 = /dev/skip enSKIP security cache control - 3 = /dec/fwmonitorFirewall packet copies + 3 = /dev/fwmonitorFirewall packet copies 16 = /dev/tap0 First Ethertap device ... 31 = /dev/tap1516th Ethertap device Regards, Roberto Nibali, ratz -- mailto: `echo [EMAIL PROTECTED] | sed 's/[NOSPAM]//g'` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
The current devices.txt is available at: http://www.lanana.org/docs/device-list/devices.txt I don't have the details for /dev/input/* in there; I need to still make that update. Small typo fix: --- devices.txt~Tue Jan 2 14:34:32 2001 +++ devices.txt Tue Jan 2 14:34:48 2001 @@ -771,7 +771,7 @@ 36 char Netlink support 0 = /dev/routeRouting, device updates, kernel to user 1 = /dev/skip enSKIP security cache control - 3 = /dec/fwmonitorFirewall packet copies + 3 = /dev/fwmonitorFirewall packet copies 16 = /dev/tap0 First Ethertap device ... 31 = /dev/tap1516th Ethertap device Regards, Roberto Nibali, ratz -- mailto: `echo [EMAIL PROTECTED] | sed 's/[NOSPAM]//g'` - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
While on this subject, the description of raw devices (char 162) in lk 2.4 is not consistent with current usage. devices.txt contains this: 162 charRaw block device interface 0 = /dev/raw Raw I/O control device 1 = /dev/raw1 First raw I/O device 2 = /dev/raw2 Second raw I/O device ... but something like this would be more accurate: 162 charRaw block device interface 0 = /dev/rawctl Raw I/O control device 1 = /dev/raw/raw1 First raw I/O device 2 = /dev/raw/raw2 Second raw I/O device ... The raw(8) command supplied in RH 6.2 and 7.0 assumes the latter structure. I have already alerted sct and this change may be coming through in one of his patches. Doug Gilbert - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
Douglas Gilbert wrote: While on this subject, the description of raw devices (char 162) in lk 2.4 is not consistent with current usage. devices.txt contains this: 162 charRaw block device interface 0 = /dev/raw Raw I/O control device 1 = /dev/raw1 First raw I/O device 2 = /dev/raw2 Second raw I/O device ... but something like this would be more accurate: 162 charRaw block device interface 0 = /dev/rawctl Raw I/O control device 1 = /dev/raw/raw1 First raw I/O device 2 = /dev/raw/raw2 Second raw I/O device ... The raw(8) command supplied in RH 6.2 and 7.0 assumes the latter structure. I have already alerted sct and this change may be coming through in one of his patches. The latter is actually better, so I certainly don't mind. sct, should I change it? -hpa -- [EMAIL PROTECTED] at work, [EMAIL PROTECTED] in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
Followup to: <[EMAIL PROTECTED]> By author:Robert Read <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > 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? > I think there are two; at least, the number will remain reserved for a long time. The current devices.txt is available at: http://www.lanana.org/docs/device-list/devices.txt I don't have the details for /dev/input/* in there; I need to still make that update. -hpa -- <[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
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/js0First joystick + 1 = /dev/input/js1Second 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 [EMAIL PROTECTED] > 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 [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
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 [EMAIL PROTECTED] > 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 [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
devices.txt inconsistency
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 [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
devices.txt inconsistency
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 [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
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/js0First joystick + 1 = /dev/input/js1Second 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: devices.txt inconsistency
Followup to: [EMAIL PROTECTED] By author:Robert Read [EMAIL PROTECTED] In newsgroup: linux.dev.kernel 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? I think there are two; at least, the number will remain reserved for a long time. The current devices.txt is available at: http://www.lanana.org/docs/device-list/devices.txt I don't have the details for /dev/input/* in there; I need to still make that update. -hpa -- [EMAIL PROTECTED] at work, [EMAIL PROTECTED] in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
