tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
Documentation: update the devices.txt documentation
Alan is no longer maintaining this list through the Linux assigned
numbers authority. Make it a collective document by referring to
"the maintainers" in plural throughout, and naming the chardev and
block layer maintainers in particular as parties of involvement.
Cut down and remove some sections that pertained to the process of
maintaining the list at lanana.org and contacting Alan directly.
Make it clear that this document, in the kernel, is the master
document.
Also move paragraphs around so as to emphasize dynamic major number
allocation.
Remove paragraph on 2.6 deprecation, that tag no longer appears
anywhere in the file.
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alan Cox <alan@linux.intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
authored by
Linus Walleij
and committed by
Greg Kroah-Hartman
ebdf4040
49db08c3
+25
-54
+1
CREDITS
+1
CREDITS
+24
-54
Documentation/devices.txt
+24
-54
Documentation/devices.txt
···
1
1
2
-
LINUX ALLOCATED DEVICES (2.6+ version)
3
-
4
-
Maintained by Alan Cox <device@lanana.org>
5
-
6
-
Last revised: 6th April 2009
2
+
LINUX ALLOCATED DEVICES (4.x+ version)
7
3
8
4
This list is the Linux Device List, the official registry of allocated
9
5
device numbers and /dev directory nodes for the Linux operating
10
6
system.
11
7
12
-
The latest version of this list is available from
13
-
http://www.lanana.org/docs/device-list/ or
14
-
ftp://ftp.kernel.org/pub/linux/docs/device-list/. This version may be
15
-
newer than the one distributed with the Linux kernel.
16
-
17
-
The LaTeX version of this document is no longer maintained.
8
+
The LaTeX version of this document is no longer maintained, nor is
9
+
the document that used to reside at lanana.org. This version in the
10
+
mainline Linux kernel is the master document. Updates shall be sent
11
+
as patches to the kernel maintainers (see the SubmittingPatches document).
12
+
Specifically explore the sections titled "CHAR and MISC DRIVERS", and
13
+
"BLOCK LAYER" in the MAINTAINERS file to find the right maintainers
14
+
to involve for character and block devices.
18
15
19
16
This document is included by reference into the Filesystem Hierarchy
20
17
Standard (FHS). The FHS is available from http://www.pathname.com/fhs/.
···
20
23
platform only. Allocations marked (68k/Atari) apply to Linux/68k on
21
24
the Atari platform only.
22
25
23
-
The symbol {2.6} means the allocation is obsolete and scheduled for
24
-
removal once kernel version 2.6 (or equivalent) is released. Some of these
25
-
allocations have already been removed.
26
-
27
-
This document is in the public domain. The author requests, however,
26
+
This document is in the public domain. The authors requests, however,
28
27
that semantically altered versions are not distributed without
29
-
permission of the author, assuming the author can be contacted without
28
+
permission of the authors, assuming the authors can be contacted without
30
29
an unreasonable effort.
31
-
32
-
In particular, please don't sent patches for this list to Linus, at
33
-
least not without contacting me first.
34
-
35
-
I do not have any information about these devices beyond what appears
36
-
on this list. Any such information requests will be deleted without
37
-
reply.
38
30
39
31
40
32
**** DEVICE DRIVERS AUTHORS PLEASE READ THIS ****
41
33
34
+
Linux now has extensive support for dynamic allocation of device numbering
35
+
and can use sysfs and udev (systemd) to handle the naming needs. There are
36
+
still some exceptions in the serial and boot device area. Before asking
37
+
for a device number make sure you actually need one.
38
+
42
39
To have a major number allocated, or a minor number in situations
43
-
where that applies (e.g. busmice), please contact me with the
44
-
appropriate device information. Also, if you have additional
45
-
information regarding any of the devices listed below, or if I have
46
-
made a mistake, I would greatly appreciate a note.
40
+
where that applies (e.g. busmice), please submit a patch and send to
41
+
the authors as indicated above.
47
42
48
-
I do, however, make a few requests about the nature of your report.
49
-
This is necessary for me to be able to keep this list up to date and
50
-
correct in a timely manner. First of all, *please* send it to the
51
-
correct address... <device@lanana.org>. I receive hundreds of email
52
-
messages a day, so mail sent to other addresses may very well get lost
53
-
in the avalanche. Please put in a descriptive subject, so I can find
54
-
your mail again should I need to. Too many people send me email
55
-
saying just "device number request" in the subject.
56
-
57
-
Second, please include a description of the device *in the same format
58
-
as this list*. The reason for this is that it is the only way I have
59
-
found to ensure I have all the requisite information to publish your
43
+
Keep the description of the device *in the same format
44
+
as this list*. The reason for this is that it is the only way we have
45
+
found to ensure we have all the requisite information to publish your
60
46
device and avoid conflicts.
61
47
62
-
Third, please don't assume that the distributed version of the list is
63
-
up to date. Due to the number of registrations I have to maintain it
64
-
in "batch mode", so there is likely additional registrations that
65
-
haven't been listed yet.
66
-
67
-
Fourth, remember that Linux now has extensive support for dynamic allocation
68
-
of device numbering and can use sysfs and udev to handle the naming needs.
69
-
There are still some exceptions in the serial and boot device area. Before
70
-
asking for a device number make sure you actually need one.
71
-
72
-
Finally, sometimes I have to play "namespace police." Please don't be
73
-
offended. I often get submissions for /dev names that would be bound
74
-
to cause conflicts down the road. I am trying to avoid getting in a
48
+
Finally, sometimes we have to play "namespace police." Please don't be
49
+
offended. We often get submissions for /dev names that would be bound
50
+
to cause conflicts down the road. We are trying to avoid getting in a
75
51
situation where we would have to suffer an incompatible forward
76
-
change. Therefore, please consult with me *before* you make your
52
+
change. Therefore, please consult with us *before* you make your
77
53
device names and numbers in any way public, at least to the point
78
54
where it would be at all difficult to get them changed.
79
55