Browse Source

vanilla linux-4.4

parazyd 2 years ago
commit
844505a0af
100 changed files with 10484 additions and 0 deletions
  1. 114 0
      .gitignore
  2. 137 0
      .mailmap
  3. 356 0
      COPYING
  4. 4089 0
      CREDITS
  5. 489 0
      Documentation/00-INDEX
  6. 87 0
      Documentation/ABI/README
  7. 5 0
      Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads
  8. 119 0
      Documentation/ABI/obsolete/sysfs-block-zram
  9. 31 0
      Documentation/ABI/obsolete/sysfs-bus-usb
  10. 29 0
      Documentation/ABI/obsolete/sysfs-class-rfkill
  11. 53 0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo
  12. 153 0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku
  13. 145 0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus
  14. 105 0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure
  15. 116 0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus
  16. 7 0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua
  17. 123 0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra
  18. 178 0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos
  19. 76 0
      Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu
  20. 12 0
      Documentation/ABI/removed/devfs
  21. 14 0
      Documentation/ABI/removed/dv1394
  22. 9 0
      Documentation/ABI/removed/ip_queue
  23. 8 0
      Documentation/ABI/removed/net_dma
  24. 10 0
      Documentation/ABI/removed/o2cb
  25. 15 0
      Documentation/ABI/removed/raw1394
  26. 16 0
      Documentation/ABI/removed/video1394
  27. 103 0
      Documentation/ABI/stable/firewire-cdev
  28. 10 0
      Documentation/ABI/stable/o2cb
  29. 10 0
      Documentation/ABI/stable/syscalls
  30. 22 0
      Documentation/ABI/stable/sysfs-acpi-pmprofile
  31. 133 0
      Documentation/ABI/stable/sysfs-bus-firewire
  32. 140 0
      Documentation/ABI/stable/sysfs-bus-usb
  33. 29 0
      Documentation/ABI/stable/sysfs-bus-vmbus
  34. 11 0
      Documentation/ABI/stable/sysfs-bus-w1
  35. 75 0
      Documentation/ABI/stable/sysfs-bus-xen-backend
  36. 56 0
      Documentation/ABI/stable/sysfs-class-backlight
  37. 67 0
      Documentation/ABI/stable/sysfs-class-rfkill
  38. 185 0
      Documentation/ABI/stable/sysfs-class-tpm
  39. 212 0
      Documentation/ABI/stable/sysfs-class-ubi
  40. 93 0
      Documentation/ABI/stable/sysfs-class-udc
  41. 10 0
      Documentation/ABI/stable/sysfs-devices
  42. 93 0
      Documentation/ABI/stable/sysfs-devices-node
  43. 25 0
      Documentation/ABI/stable/sysfs-devices-system-cpu
  44. 77 0
      Documentation/ABI/stable/sysfs-devices-system-xen_memory
  45. 189 0
      Documentation/ABI/stable/sysfs-driver-ib_srp
  46. 8 0
      Documentation/ABI/stable/sysfs-driver-qla2xxx
  47. 62 0
      Documentation/ABI/stable/sysfs-driver-usb-usbtmc
  48. 15 0
      Documentation/ABI/stable/sysfs-driver-w1_ds28e04
  49. 6 0
      Documentation/ABI/stable/sysfs-driver-w1_ds28ea00
  50. 75 0
      Documentation/ABI/stable/sysfs-firmware-efi-vars
  51. 41 0
      Documentation/ABI/stable/sysfs-firmware-opal-dump
  52. 60 0
      Documentation/ABI/stable/sysfs-firmware-opal-elog
  53. 34 0
      Documentation/ABI/stable/sysfs-module
  54. 58 0
      Documentation/ABI/stable/sysfs-transport-srp
  55. 4 0
      Documentation/ABI/stable/thermal-notification
  56. 27 0
      Documentation/ABI/stable/vdso
  57. 31 0
      Documentation/ABI/testing/configfs-spear-pcie-gadget
  58. 48 0
      Documentation/ABI/testing/configfs-stp-policy
  59. 126 0
      Documentation/ABI/testing/configfs-usb-gadget
  60. 8 0
      Documentation/ABI/testing/configfs-usb-gadget-acm
  61. 16 0
      Documentation/ABI/testing/configfs-usb-gadget-ecm
  62. 14 0
      Documentation/ABI/testing/configfs-usb-gadget-eem
  63. 9 0
      Documentation/ABI/testing/configfs-usb-gadget-ffs
  64. 11 0
      Documentation/ABI/testing/configfs-usb-gadget-hid
  65. 8 0
      Documentation/ABI/testing/configfs-usb-gadget-loopback
  66. 31 0
      Documentation/ABI/testing/configfs-usb-gadget-mass-storage
  67. 12 0
      Documentation/ABI/testing/configfs-usb-gadget-midi
  68. 15 0
      Documentation/ABI/testing/configfs-usb-gadget-ncm
  69. 9 0
      Documentation/ABI/testing/configfs-usb-gadget-obex
  70. 8 0
      Documentation/ABI/testing/configfs-usb-gadget-phonet
  71. 9 0
      Documentation/ABI/testing/configfs-usb-gadget-printer
  72. 14 0
      Documentation/ABI/testing/configfs-usb-gadget-rndis
  73. 9 0
      Documentation/ABI/testing/configfs-usb-gadget-serial
  74. 12 0
      Documentation/ABI/testing/configfs-usb-gadget-sourcesink
  75. 14 0
      Documentation/ABI/testing/configfs-usb-gadget-subset
  76. 12 0
      Documentation/ABI/testing/configfs-usb-gadget-uac1
  77. 12 0
      Documentation/ABI/testing/configfs-usb-gadget-uac2
  78. 265 0
      Documentation/ABI/testing/configfs-usb-gadget-uvc
  79. 91 0
      Documentation/ABI/testing/debugfs-driver-genwqe
  80. 20 0
      Documentation/ABI/testing/debugfs-ec
  81. 19 0
      Documentation/ABI/testing/debugfs-ideapad
  82. 16 0
      Documentation/ABI/testing/debugfs-olpc
  83. 45 0
      Documentation/ABI/testing/debugfs-pfo-nx-crypto
  84. 19 0
      Documentation/ABI/testing/debugfs-pktcdvd
  85. 110 0
      Documentation/ABI/testing/dev-kmsg
  86. 23 0
      Documentation/ABI/testing/evm
  87. 97 0
      Documentation/ABI/testing/ima_policy
  88. 22 0
      Documentation/ABI/testing/procfs-diskstats
  89. 47 0
      Documentation/ABI/testing/pstore
  90. 110 0
      Documentation/ABI/testing/sysfs-ata
  91. 237 0
      Documentation/ABI/testing/sysfs-block
  92. 156 0
      Documentation/ABI/testing/sysfs-block-bcache
  93. 47 0
      Documentation/ABI/testing/sysfs-block-dm
  94. 5 0
      Documentation/ABI/testing/sysfs-block-rssd
  95. 168 0
      Documentation/ABI/testing/sysfs-block-zram
  96. 58 0
      Documentation/ABI/testing/sysfs-bus-acpi
  97. 20 0
      Documentation/ABI/testing/sysfs-bus-amba
  98. 31 0
      Documentation/ABI/testing/sysfs-bus-bcma
  99. 24 0
      Documentation/ABI/testing/sysfs-bus-coresight-devices-etb10
  100. 0 0
      Documentation/ABI/testing/sysfs-bus-coresight-devices-etm3x

+ 114 - 0
.gitignore

@@ -0,0 +1,114 @@
1
+#
2
+# NOTE! Don't add files that are generated in specific
3
+# subdirectories here. Add them in the ".gitignore" file
4
+# in that subdirectory instead.
5
+#
6
+# NOTE! Please use 'git ls-files -i --exclude-standard'
7
+# command after changing this file, to see if there are
8
+# any tracked files which get ignored after the change.
9
+#
10
+# Normal rules
11
+#
12
+.*
13
+*.o
14
+*.o.*
15
+*.a
16
+*.s
17
+*.ko
18
+*.so
19
+*.so.dbg
20
+*.mod.c
21
+*.i
22
+*.lst
23
+*.symtypes
24
+*.order
25
+*.elf
26
+*.bin
27
+*.tar
28
+*.gz
29
+*.bz2
30
+*.lzma
31
+*.xz
32
+*.lz4
33
+*.lzo
34
+*.patch
35
+*.gcno
36
+modules.builtin
37
+Module.symvers
38
+*.dwo
39
+*.su
40
+
41
+#
42
+# Top-level generic files
43
+#
44
+/tags
45
+/TAGS
46
+/linux
47
+/vmlinux
48
+/vmlinux.32
49
+/vmlinux-gdb.py
50
+/vmlinuz
51
+/System.map
52
+/Module.markers
53
+
54
+#
55
+# Debian directory (make deb-pkg)
56
+#
57
+/debian/
58
+
59
+#
60
+# tar directory (make tar*-pkg)
61
+#
62
+/tar-install/
63
+
64
+#
65
+# git files that we don't want to ignore even it they are dot-files
66
+#
67
+!.gitignore
68
+!.mailmap
69
+
70
+#
71
+# Generated include files
72
+#
73
+include/config
74
+include/generated
75
+arch/*/include/generated
76
+
77
+# stgit generated dirs
78
+patches-*
79
+
80
+# quilt's files
81
+patches
82
+series
83
+
84
+# cscope files
85
+cscope.*
86
+ncscope.*
87
+
88
+# gnu global files
89
+GPATH
90
+GRTAGS
91
+GSYMS
92
+GTAGS
93
+
94
+# id-utils files
95
+ID
96
+
97
+*.orig
98
+*~
99
+\#*#
100
+
101
+#
102
+# Leavings from module signing
103
+#
104
+extra_certificates
105
+signing_key.pem
106
+signing_key.priv
107
+signing_key.x509
108
+x509.genkey
109
+
110
+# Kconfig presets
111
+all.config
112
+
113
+# Kdevelop4
114
+*.kdev4

+ 137 - 0
.mailmap

@@ -0,0 +1,137 @@
1
+#
2
+# This list is used by git-shortlog to fix a few botched name translations
3
+# in the git archive, either because the author's full name was messed up
4
+# and/or not always written the same way, making contributions from the
5
+# same person appearing not to be so or badly displayed.
6
+#
7
+# repo-abbrev: /pub/scm/linux/kernel/git/
8
+#
9
+
10
+Aaron Durbin <adurbin@google.com>
11
+Adam Oldham <oldhamca@gmail.com>
12
+Adam Radford <aradford@gmail.com>
13
+Adrian Bunk <bunk@stusta.de>
14
+Alan Cox <alan@lxorguk.ukuu.org.uk>
15
+Alan Cox <root@hraefn.swansea.linux.org.uk>
16
+Aleksey Gorelov <aleksey_gorelov@phoenix.com>
17
+Al Viro <viro@ftp.linux.org.uk>
18
+Al Viro <viro@zenIV.linux.org.uk>
19
+Andreas Herrmann <aherrman@de.ibm.com>
20
+Andrey Ryabinin <ryabinin.a.a@gmail.com> <a.ryabinin@samsung.com>
21
+Andrew Morton <akpm@linux-foundation.org>
22
+Andrew Vasquez <andrew.vasquez@qlogic.com>
23
+Andy Adamson <andros@citi.umich.edu>
24
+Archit Taneja <archit@ti.com>
25
+Arnaud Patard <arnaud.patard@rtp-net.org>
26
+Arnd Bergmann <arnd@arndb.de>
27
+Axel Dyks <xl@xlsigned.net>
28
+Axel Lin <axel.lin@gmail.com>
29
+Ben Gardner <bgardner@wabtec.com>
30
+Ben M Cahill <ben.m.cahill@intel.com>
31
+Björn Steinbrink <B.Steinbrink@gmx.de>
32
+Brian Avery <b.avery@hp.com>
33
+Brian King <brking@us.ibm.com>
34
+Christoph Hellwig <hch@lst.de>
35
+Corey Minyard <minyard@acm.org>
36
+Damian Hobson-Garcia <dhobsong@igel.co.jp>
37
+David Brownell <david-b@pacbell.net>
38
+David Woodhouse <dwmw2@shinybook.infradead.org>
39
+Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
40
+Domen Puncer <domen@coderock.org>
41
+Douglas Gilbert <dougg@torque.net>
42
+Ed L. Cashin <ecashin@coraid.com>
43
+Evgeniy Polyakov <johnpol@2ka.mipt.ru>
44
+Felipe W Damasio <felipewd@terra.com.br>
45
+Felix Kuhling <fxkuehl@gmx.de>
46
+Felix Moeller <felix@derklecks.de>
47
+Filipe Lautert <filipe@icewall.org>
48
+Franck Bui-Huu <vagabon.xyz@gmail.com>
49
+Frank Zago <fzago@systemfabricworks.com>
50
+Greg Kroah-Hartman <greg@echidna.(none)>
51
+Greg Kroah-Hartman <gregkh@suse.de>
52
+Greg Kroah-Hartman <greg@kroah.com>
53
+Henk Vergonet <Henk.Vergonet@gmail.com>
54
+Henrik Kretzschmar <henne@nachtwindheim.de>
55
+Henrik Rydberg <rydberg@bitmath.org>
56
+Herbert Xu <herbert@gondor.apana.org.au>
57
+Jacob Shin <Jacob.Shin@amd.com>
58
+James Bottomley <jejb@mulgrave.(none)>
59
+James Bottomley <jejb@titanic.il.steeleye.com>
60
+James E Wilson <wilson@specifix.com>
61
+James Ketrenos <jketreno@io.(none)>
62
+<javier@osg.samsung.com> <javier.martinez@collabora.co.uk>
63
+Jean Tourrilhes <jt@hpl.hp.com>
64
+Jeff Garzik <jgarzik@pretzel.yyz.us>
65
+Jens Axboe <axboe@suse.de>
66
+Jens Osterkamp <Jens.Osterkamp@de.ibm.com>
67
+John Stultz <johnstul@us.ibm.com>
68
+<josh@joshtriplett.org> <josh@freedesktop.org>
69
+<josh@joshtriplett.org> <josh@kernel.org>
70
+<josh@joshtriplett.org> <josht@linux.vnet.ibm.com>
71
+<josh@joshtriplett.org> <josht@us.ibm.com>
72
+<josh@joshtriplett.org> <josht@vnet.ibm.com>
73
+Juha Yrjola <at solidboot.com>
74
+Juha Yrjola <juha.yrjola@nokia.com>
75
+Juha Yrjola <juha.yrjola@solidboot.com>
76
+Kay Sievers <kay.sievers@vrfy.org>
77
+Kenneth W Chen <kenneth.w.chen@intel.com>
78
+Konstantin Khlebnikov <koct9i@gmail.com> <k.khlebnikov@samsung.com>
79
+Koushik <raghavendra.koushik@neterion.com>
80
+Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
81
+Leonid I Ananiev <leonid.i.ananiev@intel.com>
82
+Linas Vepstas <linas@austin.ibm.com>
83
+Mark Brown <broonie@sirena.org.uk>
84
+Matthieu CASTET <castet.matthieu@free.fr>
85
+Mayuresh Janorkar <mayur@ti.com>
86
+Michael Buesch <m@bues.ch>
87
+Michel Dänzer <michel@tungstengraphics.com>
88
+Mitesh shah <mshah@teja.com>
89
+Mohit Kumar <mohit.kumar@st.com> <mohit.kumar.dhaka@gmail.com>
90
+Morten Welinder <terra@gnome.org>
91
+Morten Welinder <welinder@anemone.rentec.com>
92
+Morten Welinder <welinder@darter.rentec.com>
93
+Morten Welinder <welinder@troll.com>
94
+Mythri P K <mythripk@ti.com>
95
+Nguyen Anh Quynh <aquynh@gmail.com>
96
+Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>
97
+Patrick Mochel <mochel@digitalimplant.org>
98
+Peter A Jonsson <pj@ludd.ltu.se>
99
+Peter Oruba <peter@oruba.de>
100
+Peter Oruba <peter.oruba@amd.com>
101
+Pratyush Anand <pratyush.anand@gmail.com> <pratyush.anand@st.com>
102
+Praveen BP <praveenbp@ti.com>
103
+Rajesh Shah <rajesh.shah@intel.com>
104
+Ralf Baechle <ralf@linux-mips.org>
105
+Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
106
+Randy Dunlap <rdunlap@infradead.org> <rdunlap@xenotime.net>
107
+Rémi Denis-Courmont <rdenis@simphalempin.com>
108
+Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
109
+Rudolf Marek <R.Marek@sh.cvut.cz>
110
+Rui Saraiva <rmps@joel.ist.utl.pt>
111
+Sachin P Sant <ssant@in.ibm.com>
112
+Sam Ravnborg <sam@mars.ravnborg.org>
113
+Santosh Shilimkar <ssantosh@kernel.org>
114
+Santosh Shilimkar <santosh.shilimkar@oracle.org>
115
+Sascha Hauer <s.hauer@pengutronix.de>
116
+S.Çağlar Onur <caglar@pardus.org.tr>
117
+Shiraz Hashim <shiraz.linux.kernel@gmail.com> <shiraz.hashim@st.com>
118
+Simon Kelley <simon@thekelleys.org.uk>
119
+Stéphane Witzmann <stephane.witzmann@ubpmes.univ-bpclermont.fr>
120
+Stephen Hemminger <shemminger@osdl.org>
121
+Sudeep Holla <sudeep.holla@arm.com> Sudeep KarkadaNagesha <sudeep.karkadanagesha@arm.com>
122
+Sumit Semwal <sumit.semwal@ti.com>
123
+Tejun Heo <htejun@gmail.com>
124
+Thomas Graf <tgraf@suug.ch>
125
+Tony Luck <tony.luck@intel.com>
126
+Tsuneo Yoshioka <Tsuneo.Yoshioka@f-secure.com>
127
+Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
128
+Uwe Kleine-König <ukl@pengutronix.de>
129
+Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com>
130
+Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
131
+Viresh Kumar <vireshk@kernel.org> <viresh.kumar@st.com>
132
+Viresh Kumar <vireshk@kernel.org> <viresh.linux@gmail.com>
133
+Viresh Kumar <vireshk@kernel.org> <viresh.kumar2@arm.com>
134
+Takashi YOSHII <takashi.yoshii.zj@renesas.com>
135
+Yusuke Goda <goda.yusuke@renesas.com>
136
+Gustavo Padovan <gustavo@las.ic.unicamp.br>
137
+Gustavo Padovan <padovan@profusion.mobi>

+ 356 - 0
COPYING

@@ -0,0 +1,356 @@
1
+
2
+   NOTE! This copyright does *not* cover user programs that use kernel
3
+ services by normal system calls - this is merely considered normal use
4
+ of the kernel, and does *not* fall under the heading of "derived work".
5
+ Also note that the GPL below is copyrighted by the Free Software
6
+ Foundation, but the instance of code that it refers to (the Linux
7
+ kernel) is copyrighted by me and others who actually wrote it.
8
+
9
+ Also note that the only valid version of the GPL as far as the kernel
10
+ is concerned is _this_ particular version of the license (ie v2, not
11
+ v2.2 or v3.x or whatever), unless explicitly otherwise stated.
12
+
13
+			Linus Torvalds
14
+
15
+----------------------------------------
16
+
17
+		    GNU GENERAL PUBLIC LICENSE
18
+		       Version 2, June 1991
19
+
20
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
21
+                       51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
22
+ Everyone is permitted to copy and distribute verbatim copies
23
+ of this license document, but changing it is not allowed.
24
+
25
+			    Preamble
26
+
27
+  The licenses for most software are designed to take away your
28
+freedom to share and change it.  By contrast, the GNU General Public
29
+License is intended to guarantee your freedom to share and change free
30
+software--to make sure the software is free for all its users.  This
31
+General Public License applies to most of the Free Software
32
+Foundation's software and to any other program whose authors commit to
33
+using it.  (Some other Free Software Foundation software is covered by
34
+the GNU Library General Public License instead.)  You can apply it to
35
+your programs, too.
36
+
37
+  When we speak of free software, we are referring to freedom, not
38
+price.  Our General Public Licenses are designed to make sure that you
39
+have the freedom to distribute copies of free software (and charge for
40
+this service if you wish), that you receive source code or can get it
41
+if you want it, that you can change the software or use pieces of it
42
+in new free programs; and that you know you can do these things.
43
+
44
+  To protect your rights, we need to make restrictions that forbid
45
+anyone to deny you these rights or to ask you to surrender the rights.
46
+These restrictions translate to certain responsibilities for you if you
47
+distribute copies of the software, or if you modify it.
48
+
49
+  For example, if you distribute copies of such a program, whether
50
+gratis or for a fee, you must give the recipients all the rights that
51
+you have.  You must make sure that they, too, receive or can get the
52
+source code.  And you must show them these terms so they know their
53
+rights.
54
+
55
+  We protect your rights with two steps: (1) copyright the software, and
56
+(2) offer you this license which gives you legal permission to copy,
57
+distribute and/or modify the software.
58
+
59
+  Also, for each author's protection and ours, we want to make certain
60
+that everyone understands that there is no warranty for this free
61
+software.  If the software is modified by someone else and passed on, we
62
+want its recipients to know that what they have is not the original, so
63
+that any problems introduced by others will not reflect on the original
64
+authors' reputations.
65
+
66
+  Finally, any free program is threatened constantly by software
67
+patents.  We wish to avoid the danger that redistributors of a free
68
+program will individually obtain patent licenses, in effect making the
69
+program proprietary.  To prevent this, we have made it clear that any
70
+patent must be licensed for everyone's free use or not licensed at all.
71
+
72
+  The precise terms and conditions for copying, distribution and
73
+modification follow.
74
+
75
+		    GNU GENERAL PUBLIC LICENSE
76
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
77
+
78
+  0. This License applies to any program or other work which contains
79
+a notice placed by the copyright holder saying it may be distributed
80
+under the terms of this General Public License.  The "Program", below,
81
+refers to any such program or work, and a "work based on the Program"
82
+means either the Program or any derivative work under copyright law:
83
+that is to say, a work containing the Program or a portion of it,
84
+either verbatim or with modifications and/or translated into another
85
+language.  (Hereinafter, translation is included without limitation in
86
+the term "modification".)  Each licensee is addressed as "you".
87
+
88
+Activities other than copying, distribution and modification are not
89
+covered by this License; they are outside its scope.  The act of
90
+running the Program is not restricted, and the output from the Program
91
+is covered only if its contents constitute a work based on the
92
+Program (independent of having been made by running the Program).
93
+Whether that is true depends on what the Program does.
94
+
95
+  1. You may copy and distribute verbatim copies of the Program's
96
+source code as you receive it, in any medium, provided that you
97
+conspicuously and appropriately publish on each copy an appropriate
98
+copyright notice and disclaimer of warranty; keep intact all the
99
+notices that refer to this License and to the absence of any warranty;
100
+and give any other recipients of the Program a copy of this License
101
+along with the Program.
102
+
103
+You may charge a fee for the physical act of transferring a copy, and
104
+you may at your option offer warranty protection in exchange for a fee.
105
+
106
+  2. You may modify your copy or copies of the Program or any portion
107
+of it, thus forming a work based on the Program, and copy and
108
+distribute such modifications or work under the terms of Section 1
109
+above, provided that you also meet all of these conditions:
110
+
111
+    a) You must cause the modified files to carry prominent notices
112
+    stating that you changed the files and the date of any change.
113
+
114
+    b) You must cause any work that you distribute or publish, that in
115
+    whole or in part contains or is derived from the Program or any
116
+    part thereof, to be licensed as a whole at no charge to all third
117
+    parties under the terms of this License.
118
+
119
+    c) If the modified program normally reads commands interactively
120
+    when run, you must cause it, when started running for such
121
+    interactive use in the most ordinary way, to print or display an
122
+    announcement including an appropriate copyright notice and a
123
+    notice that there is no warranty (or else, saying that you provide
124
+    a warranty) and that users may redistribute the program under
125
+    these conditions, and telling the user how to view a copy of this
126
+    License.  (Exception: if the Program itself is interactive but
127
+    does not normally print such an announcement, your work based on
128
+    the Program is not required to print an announcement.)
129
+
130
+These requirements apply to the modified work as a whole.  If
131
+identifiable sections of that work are not derived from the Program,
132
+and can be reasonably considered independent and separate works in
133
+themselves, then this License, and its terms, do not apply to those
134
+sections when you distribute them as separate works.  But when you
135
+distribute the same sections as part of a whole which is a work based
136
+on the Program, the distribution of the whole must be on the terms of
137
+this License, whose permissions for other licensees extend to the
138
+entire whole, and thus to each and every part regardless of who wrote it.
139
+
140
+Thus, it is not the intent of this section to claim rights or contest
141
+your rights to work written entirely by you; rather, the intent is to
142
+exercise the right to control the distribution of derivative or
143
+collective works based on the Program.
144
+
145
+In addition, mere aggregation of another work not based on the Program
146
+with the Program (or with a work based on the Program) on a volume of
147
+a storage or distribution medium does not bring the other work under
148
+the scope of this License.
149
+
150
+  3. You may copy and distribute the Program (or a work based on it,
151
+under Section 2) in object code or executable form under the terms of
152
+Sections 1 and 2 above provided that you also do one of the following:
153
+
154
+    a) Accompany it with the complete corresponding machine-readable
155
+    source code, which must be distributed under the terms of Sections
156
+    1 and 2 above on a medium customarily used for software interchange; or,
157
+
158
+    b) Accompany it with a written offer, valid for at least three
159
+    years, to give any third party, for a charge no more than your
160
+    cost of physically performing source distribution, a complete
161
+    machine-readable copy of the corresponding source code, to be
162
+    distributed under the terms of Sections 1 and 2 above on a medium
163
+    customarily used for software interchange; or,
164
+
165
+    c) Accompany it with the information you received as to the offer
166
+    to distribute corresponding source code.  (This alternative is
167
+    allowed only for noncommercial distribution and only if you
168
+    received the program in object code or executable form with such
169
+    an offer, in accord with Subsection b above.)
170
+
171
+The source code for a work means the preferred form of the work for
172
+making modifications to it.  For an executable work, complete source
173
+code means all the source code for all modules it contains, plus any
174
+associated interface definition files, plus the scripts used to
175
+control compilation and installation of the executable.  However, as a
176
+special exception, the source code distributed need not include
177
+anything that is normally distributed (in either source or binary
178
+form) with the major components (compiler, kernel, and so on) of the
179
+operating system on which the executable runs, unless that component
180
+itself accompanies the executable.
181
+
182
+If distribution of executable or object code is made by offering
183
+access to copy from a designated place, then offering equivalent
184
+access to copy the source code from the same place counts as
185
+distribution of the source code, even though third parties are not
186
+compelled to copy the source along with the object code.
187
+
188
+  4. You may not copy, modify, sublicense, or distribute the Program
189
+except as expressly provided under this License.  Any attempt
190
+otherwise to copy, modify, sublicense or distribute the Program is
191
+void, and will automatically terminate your rights under this License.
192
+However, parties who have received copies, or rights, from you under
193
+this License will not have their licenses terminated so long as such
194
+parties remain in full compliance.
195
+
196
+  5. You are not required to accept this License, since you have not
197
+signed it.  However, nothing else grants you permission to modify or
198
+distribute the Program or its derivative works.  These actions are
199
+prohibited by law if you do not accept this License.  Therefore, by
200
+modifying or distributing the Program (or any work based on the
201
+Program), you indicate your acceptance of this License to do so, and
202
+all its terms and conditions for copying, distributing or modifying
203
+the Program or works based on it.
204
+
205
+  6. Each time you redistribute the Program (or any work based on the
206
+Program), the recipient automatically receives a license from the
207
+original licensor to copy, distribute or modify the Program subject to
208
+these terms and conditions.  You may not impose any further
209
+restrictions on the recipients' exercise of the rights granted herein.
210
+You are not responsible for enforcing compliance by third parties to
211
+this License.
212
+
213
+  7. If, as a consequence of a court judgment or allegation of patent
214
+infringement or for any other reason (not limited to patent issues),
215
+conditions are imposed on you (whether by court order, agreement or
216
+otherwise) that contradict the conditions of this License, they do not
217
+excuse you from the conditions of this License.  If you cannot
218
+distribute so as to satisfy simultaneously your obligations under this
219
+License and any other pertinent obligations, then as a consequence you
220
+may not distribute the Program at all.  For example, if a patent
221
+license would not permit royalty-free redistribution of the Program by
222
+all those who receive copies directly or indirectly through you, then
223
+the only way you could satisfy both it and this License would be to
224
+refrain entirely from distribution of the Program.
225
+
226
+If any portion of this section is held invalid or unenforceable under
227
+any particular circumstance, the balance of the section is intended to
228
+apply and the section as a whole is intended to apply in other
229
+circumstances.
230
+
231
+It is not the purpose of this section to induce you to infringe any
232
+patents or other property right claims or to contest validity of any
233
+such claims; this section has the sole purpose of protecting the
234
+integrity of the free software distribution system, which is
235
+implemented by public license practices.  Many people have made
236
+generous contributions to the wide range of software distributed
237
+through that system in reliance on consistent application of that
238
+system; it is up to the author/donor to decide if he or she is willing
239
+to distribute software through any other system and a licensee cannot
240
+impose that choice.
241
+
242
+This section is intended to make thoroughly clear what is believed to
243
+be a consequence of the rest of this License.
244
+
245
+  8. If the distribution and/or use of the Program is restricted in
246
+certain countries either by patents or by copyrighted interfaces, the
247
+original copyright holder who places the Program under this License
248
+may add an explicit geographical distribution limitation excluding
249
+those countries, so that distribution is permitted only in or among
250
+countries not thus excluded.  In such case, this License incorporates
251
+the limitation as if written in the body of this License.
252
+
253
+  9. The Free Software Foundation may publish revised and/or new versions
254
+of the General Public License from time to time.  Such new versions will
255
+be similar in spirit to the present version, but may differ in detail to
256
+address new problems or concerns.
257
+
258
+Each version is given a distinguishing version number.  If the Program
259
+specifies a version number of this License which applies to it and "any
260
+later version", you have the option of following the terms and conditions
261
+either of that version or of any later version published by the Free
262
+Software Foundation.  If the Program does not specify a version number of
263
+this License, you may choose any version ever published by the Free Software
264
+Foundation.
265
+
266
+  10. If you wish to incorporate parts of the Program into other free
267
+programs whose distribution conditions are different, write to the author
268
+to ask for permission.  For software which is copyrighted by the Free
269
+Software Foundation, write to the Free Software Foundation; we sometimes
270
+make exceptions for this.  Our decision will be guided by the two goals
271
+of preserving the free status of all derivatives of our free software and
272
+of promoting the sharing and reuse of software generally.
273
+
274
+			    NO WARRANTY
275
+
276
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
277
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
278
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
279
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
280
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
281
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
282
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
283
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
284
+REPAIR OR CORRECTION.
285
+
286
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
287
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
288
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
289
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
290
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
291
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
292
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
293
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
294
+POSSIBILITY OF SUCH DAMAGES.
295
+
296
+		     END OF TERMS AND CONDITIONS
297
+
298
+	    How to Apply These Terms to Your New Programs
299
+
300
+  If you develop a new program, and you want it to be of the greatest
301
+possible use to the public, the best way to achieve this is to make it
302
+free software which everyone can redistribute and change under these terms.
303
+
304
+  To do so, attach the following notices to the program.  It is safest
305
+to attach them to the start of each source file to most effectively
306
+convey the exclusion of warranty; and each file should have at least
307
+the "copyright" line and a pointer to where the full notice is found.
308
+
309
+    <one line to give the program's name and a brief idea of what it does.>
310
+    Copyright (C) <year>  <name of author>
311
+
312
+    This program is free software; you can redistribute it and/or modify
313
+    it under the terms of the GNU General Public License as published by
314
+    the Free Software Foundation; either version 2 of the License, or
315
+    (at your option) any later version.
316
+
317
+    This program is distributed in the hope that it will be useful,
318
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
319
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
320
+    GNU General Public License for more details.
321
+
322
+    You should have received a copy of the GNU General Public License
323
+    along with this program; if not, write to the Free Software
324
+    Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
325
+
326
+
327
+Also add information on how to contact you by electronic and paper mail.
328
+
329
+If the program is interactive, make it output a short notice like this
330
+when it starts in an interactive mode:
331
+
332
+    Gnomovision version 69, Copyright (C) year name of author
333
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
334
+    This is free software, and you are welcome to redistribute it
335
+    under certain conditions; type `show c' for details.
336
+
337
+The hypothetical commands `show w' and `show c' should show the appropriate
338
+parts of the General Public License.  Of course, the commands you use may
339
+be called something other than `show w' and `show c'; they could even be
340
+mouse-clicks or menu items--whatever suits your program.
341
+
342
+You should also get your employer (if you work as a programmer) or your
343
+school, if any, to sign a "copyright disclaimer" for the program, if
344
+necessary.  Here is a sample; alter the names:
345
+
346
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
347
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
348
+
349
+  <signature of Ty Coon>, 1 April 1989
350
+  Ty Coon, President of Vice
351
+
352
+This General Public License does not permit incorporating your program into
353
+proprietary programs.  If your program is a subroutine library, you may
354
+consider it more useful to permit linking proprietary applications with the
355
+library.  If this is what you want to do, use the GNU Library General
356
+Public License instead of this License.

File diff suppressed because it is too large
+ 4089 - 0
CREDITS


+ 489 - 0
Documentation/00-INDEX

@@ -0,0 +1,489 @@
1
+
2
+This is a brief list of all the files in ./linux/Documentation and what
3
+they contain. If you add a documentation file, please list it here in
4
+alphabetical order as well, or risk being hunted down like a rabid dog.
5
+Please keep the descriptions small enough to fit on one line.
6
+							 Thanks -- Paul G.
7
+
8
+Following translations are available on the WWW:
9
+
10
+   - Japanese, maintained by the JF Project (jf@listserv.linux.or.jp), at
11
+     http://linuxjf.sourceforge.jp/
12
+
13
+00-INDEX
14
+	- this file.
15
+ABI/
16
+	- info on kernel <-> userspace ABI and relative interface stability.
17
+
18
+BUG-HUNTING
19
+	- brute force method of doing binary search of patches to find bug.
20
+Changes
21
+	- list of changes that break older software packages.
22
+CodingStyle
23
+	- how the maintainers expect the C code in the kernel to look.
24
+DMA-API.txt
25
+	- DMA API, pci_ API & extensions for non-consistent memory machines.
26
+DMA-API-HOWTO.txt
27
+	- Dynamic DMA mapping Guide
28
+DMA-ISA-LPC.txt
29
+	- How to do DMA with ISA (and LPC) devices.
30
+DMA-attributes.txt
31
+	- listing of the various possible attributes a DMA region can have
32
+DocBook/
33
+	- directory with DocBook templates etc. for kernel documentation.
34
+EDID/
35
+	- directory with info on customizing EDID for broken gfx/displays.
36
+HOWTO
37
+	- the process and procedures of how to do Linux kernel development.
38
+IPMI.txt
39
+	- info on Linux Intelligent Platform Management Interface (IPMI) Driver.
40
+IRQ-affinity.txt
41
+	- how to select which CPU(s) handle which interrupt events on SMP.
42
+IRQ-domain.txt
43
+	- info on interrupt numbering and setting up IRQ domains.
44
+IRQ.txt
45
+	- description of what an IRQ is.
46
+Intel-IOMMU.txt
47
+	- basic info on the Intel IOMMU virtualization support.
48
+Makefile
49
+	- some files in Documentation dir are actually sample code to build
50
+ManagementStyle
51
+	- how to (attempt to) manage kernel hackers.
52
+RCU/
53
+	- directory with info on RCU (read-copy update).
54
+SAK.txt
55
+	- info on Secure Attention Keys.
56
+SM501.txt
57
+	- Silicon Motion SM501 multimedia companion chip
58
+SecurityBugs
59
+	- procedure for reporting security bugs found in the kernel.
60
+SubmitChecklist
61
+	- Linux kernel patch submission checklist.
62
+SubmittingDrivers
63
+	- procedure to get a new driver source included into the kernel tree.
64
+SubmittingPatches
65
+	- procedure to get a source patch included into the kernel tree.
66
+VGA-softcursor.txt
67
+	- how to change your VGA cursor from a blinking underscore.
68
+accounting/
69
+	- documentation on accounting and taskstats.
70
+acpi/
71
+	- info on ACPI-specific hooks in the kernel.
72
+aoe/
73
+	- description of AoE (ATA over Ethernet) along with config examples.
74
+applying-patches.txt
75
+	- description of various trees and how to apply their patches.
76
+arm/
77
+	- directory with info about Linux on the ARM architecture.
78
+arm64/
79
+	- directory with info about Linux on the 64 bit ARM architecture.
80
+assoc_array.txt
81
+	- generic associative array intro.
82
+atomic_ops.txt
83
+	- semantics and behavior of atomic and bitmask operations.
84
+auxdisplay/
85
+	- misc. LCD driver documentation (cfag12864b, ks0108).
86
+backlight/
87
+	- directory with info on controlling backlights in flat panel displays
88
+bad_memory.txt
89
+	- how to use kernel parameters to exclude bad RAM regions.
90
+basic_profiling.txt
91
+	- basic instructions for those who wants to profile Linux kernel.
92
+bcache.txt
93
+	- Block-layer cache on fast SSDs to improve slow (raid) I/O performance.
94
+binfmt_misc.txt
95
+	- info on the kernel support for extra binary formats.
96
+blackfin/
97
+	- directory with documentation for the Blackfin arch.
98
+block/
99
+	- info on the Block I/O (BIO) layer.
100
+blockdev/
101
+	- info on block devices & drivers
102
+braille-console.txt
103
+	- info on how to use serial devices for Braille support.
104
+bt8xxgpio.txt
105
+	- info on how to modify a bt8xx video card for GPIO usage.
106
+btmrvl.txt
107
+	- info on Marvell Bluetooth driver usage.
108
+bus-devices/
109
+	- directory with info on TI GPMC (General Purpose Memory Controller)
110
+bus-virt-phys-mapping.txt
111
+	- how to access I/O mapped memory from within device drivers.
112
+cachetlb.txt
113
+	- describes the cache/TLB flushing interfaces Linux uses.
114
+cdrom/
115
+	- directory with information on the CD-ROM drivers that Linux has.
116
+cgroups/
117
+	- cgroups features, including cpusets and memory controller.
118
+circular-buffers.txt
119
+	- how to make use of the existing circular buffer infrastructure
120
+clk.txt
121
+	- info on the common clock framework
122
+coccinelle.txt
123
+	- info on how to get and use the Coccinelle code checking tool.
124
+connector/
125
+	- docs on the netlink based userspace<->kernel space communication mod.
126
+console/
127
+	- documentation on Linux console drivers.
128
+cpu-freq/
129
+	- info on CPU frequency and voltage scaling.
130
+cpu-hotplug.txt
131
+	- document describing CPU hotplug support in the Linux kernel.
132
+cpu-load.txt
133
+	- document describing how CPU load statistics are collected.
134
+cpuidle/
135
+	- info on CPU_IDLE, CPU idle state management subsystem.
136
+cputopology.txt
137
+	- documentation on how CPU topology info is exported via sysfs.
138
+crc32.txt
139
+	- brief tutorial on CRC computation
140
+cris/
141
+	- directory with info about Linux on CRIS architecture.
142
+crypto/
143
+	- directory with info on the Crypto API.
144
+dcdbas.txt
145
+	- information on the Dell Systems Management Base Driver.
146
+debugging-modules.txt
147
+	- some notes on debugging modules after Linux 2.6.3.
148
+debugging-via-ohci1394.txt
149
+	- how to use firewire like a hardware debugger memory reader.
150
+dell_rbu.txt
151
+	- document demonstrating the use of the Dell Remote BIOS Update driver.
152
+development-process/
153
+	- how to work with the mainline kernel development process.
154
+device-mapper/
155
+	- directory with info on Device Mapper.
156
+devices.txt
157
+	- plain ASCII listing of all the nodes in /dev/ with major minor #'s.
158
+devicetree/
159
+	- directory with info on device tree files used by OF/PowerPC/ARM
160
+digsig.txt
161
+	-info on the Digital Signature Verification API
162
+dma-buf-sharing.txt
163
+	- the DMA Buffer Sharing API Guide
164
+dontdiff
165
+	- file containing a list of files that should never be diff'ed.
166
+driver-model/
167
+	- directory with info about Linux driver model.
168
+dvb/
169
+	- info on Linux Digital Video Broadcast (DVB) subsystem.
170
+dynamic-debug-howto.txt
171
+	- how to use the dynamic debug (dyndbg) feature.
172
+early-userspace/
173
+	- info about initramfs, klibc, and userspace early during boot.
174
+edac.txt
175
+	- information on EDAC - Error Detection And Correction
176
+efi-stub.txt
177
+	- How to use the EFI boot stub to bypass GRUB or elilo on EFI systems.
178
+eisa.txt
179
+	- info on EISA bus support.
180
+email-clients.txt
181
+	- info on how to use e-mail to send un-mangled (git) patches.
182
+extcon/
183
+	- directory with porting guide for Android kernel switch driver.
184
+fault-injection/
185
+	- dir with docs about the fault injection capabilities infrastructure.
186
+fb/
187
+	- directory with info on the frame buffer graphics abstraction layer.
188
+filesystems/
189
+	- info on the vfs and the various filesystems that Linux supports.
190
+firmware_class/
191
+	- request_firmware() hotplug interface info.
192
+flexible-arrays.txt
193
+	- how to make use of flexible sized arrays in linux
194
+fmc/
195
+	- information about the FMC bus abstraction
196
+frv/
197
+	- Fujitsu FR-V Linux documentation.
198
+futex-requeue-pi.txt
199
+	- info on requeueing of tasks from a non-PI futex to a PI futex
200
+gcov.txt
201
+	- use of GCC's coverage testing tool "gcov" with the Linux kernel
202
+gpio/
203
+	- gpio related documentation
204
+hid/
205
+	- directory with information on human interface devices
206
+highuid.txt
207
+	- notes on the change from 16 bit to 32 bit user/group IDs.
208
+hsi.txt
209
+	- HSI subsystem overview.
210
+hwspinlock.txt
211
+	- hardware spinlock provides hardware assistance for synchronization
212
+timers/
213
+	- info on the timer related topics
214
+hw_random.txt
215
+	- info on Linux support for random number generator in i8xx chipsets.
216
+hwmon/
217
+	- directory with docs on various hardware monitoring drivers.
218
+i2c/
219
+	- directory with info about the I2C bus/protocol (2 wire, kHz speed).
220
+i2o/
221
+	- directory with info about the Linux I2O subsystem.
222
+x86/i386/
223
+	- directory with info about Linux on Intel 32 bit architecture.
224
+ia64/
225
+	- directory with info about Linux on Intel 64 bit architecture.
226
+infiniband/
227
+	- directory with documents concerning Linux InfiniBand support.
228
+init.txt
229
+	- what to do when the kernel can't find the 1st process to run.
230
+initrd.txt
231
+	- how to use the RAM disk as an initial/temporary root filesystem.
232
+input/
233
+	- info on Linux input device support.
234
+intel_txt.txt
235
+	- info on intel Trusted Execution Technology (intel TXT).
236
+io-mapping.txt
237
+	- description of io_mapping functions in linux/io-mapping.h
238
+io_ordering.txt
239
+	- info on ordering I/O writes to memory-mapped addresses.
240
+ioctl/
241
+	- directory with documents describing various IOCTL calls.
242
+iostats.txt
243
+	- info on I/O statistics Linux kernel provides.
244
+irqflags-tracing.txt
245
+	- how to use the irq-flags tracing feature.
246
+isapnp.txt
247
+	- info on Linux ISA Plug & Play support.
248
+isdn/
249
+	- directory with info on the Linux ISDN support, and supported cards.
250
+java.txt
251
+	- info on the in-kernel binary support for Java(tm).
252
+ja_JP/
253
+	- directory with Japanese translations of various documents
254
+kbuild/
255
+	- directory with info about the kernel build process.
256
+kdump/
257
+	- directory with mini HowTo on getting the crash dump code to work.
258
+kernel-doc-nano-HOWTO.txt
259
+	- mini HowTo on generation and location of kernel documentation files.
260
+kernel-docs.txt
261
+	- listing of various WWW + books that document kernel internals.
262
+kernel-parameters.txt
263
+	- summary listing of command line / boot prompt args for the kernel.
264
+kernel-per-CPU-kthreads.txt
265
+	- List of all per-CPU kthreads and how they introduce jitter.
266
+kmemcheck.txt
267
+	- info on dynamic checker that detects uses of uninitialized memory.
268
+kmemleak.txt
269
+	- info on how to make use of the kernel memory leak detection system
270
+ko_KR/
271
+	- directory with Korean translations of various documents
272
+kobject.txt
273
+	- info of the kobject infrastructure of the Linux kernel.
274
+kprobes.txt
275
+	- documents the kernel probes debugging feature.
276
+kref.txt
277
+	- docs on adding reference counters (krefs) to kernel objects.
278
+kselftest.txt
279
+	- small unittests for (some) individual codepaths in the kernel.
280
+laptops/
281
+	- directory with laptop related info and laptop driver documentation.
282
+ldm.txt
283
+	- a brief description of LDM (Windows Dynamic Disks).
284
+leds/
285
+	- directory with info about LED handling under Linux.
286
+local_ops.txt
287
+	- semantics and behavior of local atomic operations.
288
+locking/
289
+	- directory with info about kernel locking primitives
290
+lockup-watchdogs.txt
291
+	- info on soft and hard lockup detectors (aka nmi_watchdog).
292
+logo.gif
293
+	- full colour GIF image of Linux logo (penguin - Tux).
294
+logo.txt
295
+	- info on creator of above logo & site to get additional images from.
296
+lzo.txt
297
+	- kernel LZO decompressor input formats
298
+m68k/
299
+	- directory with info about Linux on Motorola 68k architecture.
300
+magic-number.txt
301
+	- list of magic numbers used to mark/protect kernel data structures.
302
+mailbox.txt
303
+	- How to write drivers for the common mailbox framework (IPC).
304
+md.txt
305
+	- info on boot arguments for the multiple devices driver.
306
+media-framework.txt
307
+	- info on media framework, its data structures, functions and usage.
308
+memory-barriers.txt
309
+	- info on Linux kernel memory barriers.
310
+memory-devices/
311
+	- directory with info on parts like the Texas Instruments EMIF driver
312
+memory-hotplug.txt
313
+	- Hotpluggable memory support, how to use and current status.
314
+metag/
315
+	- directory with info about Linux on Meta architecture.
316
+mips/
317
+	- directory with info about Linux on MIPS architecture.
318
+misc-devices/
319
+	- directory with info about devices using the misc dev subsystem
320
+mmc/
321
+	- directory with info about the MMC subsystem
322
+mn10300/
323
+	- directory with info about the mn10300 architecture port
324
+module-signing.txt
325
+	- Kernel module signing for increased security when loading modules.
326
+mtd/
327
+	- directory with info about memory technology devices (flash)
328
+mono.txt
329
+	- how to execute Mono-based .NET binaries with the help of BINFMT_MISC.
330
+namespaces/
331
+	- directory with various information about namespaces
332
+netlabel/
333
+	- directory with information on the NetLabel subsystem.
334
+networking/
335
+	- directory with info on various aspects of networking with Linux.
336
+nfc/
337
+	- directory relating info about Near Field Communications support.
338
+nommu-mmap.txt
339
+	- documentation about no-mmu memory mapping support.
340
+numastat.txt
341
+	- info on how to read Numa policy hit/miss statistics in sysfs.
342
+oops-tracing.txt
343
+	- how to decode those nasty internal kernel error dump messages.
344
+padata.txt
345
+	- An introduction to the "padata" parallel execution API
346
+parisc/
347
+	- directory with info on using Linux on PA-RISC architecture.
348
+parport.txt
349
+	- how to use the parallel-port driver.
350
+parport-lowlevel.txt
351
+	- description and usage of the low level parallel port functions.
352
+pcmcia/
353
+	- info on the Linux PCMCIA driver.
354
+percpu-rw-semaphore.txt
355
+	- RCU based read-write semaphore optimized for locking for reading
356
+phy.txt
357
+	- Description of the generic PHY framework.
358
+pi-futex.txt
359
+	- documentation on lightweight priority inheritance futexes.
360
+pinctrl.txt
361
+	- info on pinctrl subsystem and the PINMUX/PINCONF and drivers
362
+pnp.txt
363
+	- Linux Plug and Play documentation.
364
+power/
365
+	- directory with info on Linux PCI power management.
366
+powerpc/
367
+	- directory with info on using Linux with the PowerPC.
368
+prctl/
369
+	- directory with info on the priveledge control subsystem
370
+preempt-locking.txt
371
+	- info on locking under a preemptive kernel.
372
+printk-formats.txt
373
+	- how to get printk format specifiers right
374
+pps/
375
+	- directory with information on the pulse-per-second support
376
+ptp/
377
+	- directory with info on support for IEEE 1588 PTP clocks in Linux.
378
+pwm.txt
379
+	- info on the pulse width modulation driver subsystem
380
+ramoops.txt
381
+	- documentation of the ramoops oops/panic logging module.
382
+rapidio/
383
+	- directory with info on RapidIO packet-based fabric interconnect
384
+rbtree.txt
385
+	- info on what red-black trees are and what they are for.
386
+remoteproc.txt
387
+	- info on how to handle remote processor (e.g. AMP) offloads/usage.
388
+rfkill.txt
389
+	- info on the radio frequency kill switch subsystem/support.
390
+robust-futex-ABI.txt
391
+	- documentation of the robust futex ABI.
392
+robust-futexes.txt
393
+	- a description of what robust futexes are.
394
+rpmsg.txt
395
+	- info on the Remote Processor Messaging (rpmsg) Framework
396
+rtc.txt
397
+	- notes on how to use the Real Time Clock (aka CMOS clock) driver.
398
+s390/
399
+	- directory with info on using Linux on the IBM S390.
400
+scheduler/
401
+	- directory with info on the scheduler.
402
+scsi/
403
+	- directory with info on Linux scsi support.
404
+security/
405
+	- directory that contains security-related info
406
+serial/
407
+	- directory with info on the low level serial API.
408
+serial-console.txt
409
+	- how to set up Linux with a serial line console as the default.
410
+sgi-ioc4.txt
411
+	- description of the SGI IOC4 PCI (multi function) device.
412
+sh/
413
+	- directory with info on porting Linux to a new architecture.
414
+smsc_ece1099.txt
415
+	-info on the smsc Keyboard Scan Expansion/GPIO Expansion device.
416
+sound/
417
+	- directory with info on sound card support.
418
+sparse.txt
419
+	- info on how to obtain and use the sparse tool for typechecking.
420
+spi/
421
+	- overview of Linux kernel Serial Peripheral Interface (SPI) support.
422
+stable_api_nonsense.txt
423
+	- info on why the kernel does not have a stable in-kernel api or abi.
424
+stable_kernel_rules.txt
425
+	- rules and procedures for the -stable kernel releases.
426
+static-keys.txt
427
+	- info on how static keys allow debug code in hotpaths via patching
428
+svga.txt
429
+	- short guide on selecting video modes at boot via VGA BIOS.
430
+sysfs-rules.txt
431
+	- How not to use sysfs.
432
+sysctl/
433
+	- directory with info on the /proc/sys/* files.
434
+sysrq.txt
435
+	- info on the magic SysRq key.
436
+target/
437
+	- directory with info on generating TCM v4 fabric .ko modules
438
+this_cpu_ops.txt
439
+	- List rationale behind and the way to use this_cpu operations.
440
+thermal/
441
+	- directory with information on managing thermal issues (CPU/temp)
442
+trace/
443
+	- directory with info on tracing technologies within linux
444
+unaligned-memory-access.txt
445
+	- info on how to avoid arch breaking unaligned memory access in code.
446
+unicode.txt
447
+	- info on the Unicode character/font mapping used in Linux.
448
+unshare.txt
449
+	- description of the Linux unshare system call.
450
+usb/
451
+	- directory with info regarding the Universal Serial Bus.
452
+vDSO/
453
+	- directory with info regarding virtual dynamic shared objects
454
+vfio.txt
455
+	- info on Virtual Function I/O used in guest/hypervisor instances.
456
+vgaarbiter.txt
457
+	- info on enable/disable the legacy decoding on different VGA devices
458
+video-output.txt
459
+	- sysfs class driver interface to enable/disable a video output device.
460
+video4linux/
461
+	- directory with info regarding video/TV/radio cards and linux.
462
+virtual/
463
+	- directory with information on the various linux virtualizations.
464
+vm/
465
+	- directory with info on the Linux vm code.
466
+vme_api.txt
467
+	- file relating info on the VME bus API in linux
468
+volatile-considered-harmful.txt
469
+	- Why the "volatile" type class should not be used
470
+w1/
471
+	- directory with documents regarding the 1-wire (w1) subsystem.
472
+watchdog/
473
+	- how to auto-reboot Linux if it has "fallen and can't get up". ;-)
474
+wimax/
475
+	- directory with info about Intel Wireless Wimax Connections
476
+workqueue.txt
477
+	- information on the Concurrency Managed Workqueue implementation
478
+x86/x86_64/
479
+	- directory with info on Linux support for AMD x86-64 (Hammer) machines.
480
+xillybus.txt
481
+	- Overview and basic ui of xillybus driver
482
+xtensa/
483
+	- directory with documents relating to arch/xtensa port/implementation
484
+xz.txt
485
+	- how to make use of the XZ data compression within linux kernel
486
+zh_CN/
487
+	- directory with Chinese translations of various documents
488
+zorro.txt
489
+	- info on writing drivers for Zorro bus devices found on Amigas.

+ 87 - 0
Documentation/ABI/README

@@ -0,0 +1,87 @@
1
+This directory attempts to document the ABI between the Linux kernel and
2
+userspace, and the relative stability of these interfaces.  Due to the
3
+everchanging nature of Linux, and the differing maturity levels, these
4
+interfaces should be used by userspace programs in different ways.
5
+
6
+We have four different levels of ABI stability, as shown by the four
7
+different subdirectories in this location.  Interfaces may change levels
8
+of stability according to the rules described below.
9
+
10
+The different levels of stability are:
11
+
12
+  stable/
13
+	This directory documents the interfaces that the developer has
14
+	defined to be stable.  Userspace programs are free to use these
15
+	interfaces with no restrictions, and backward compatibility for
16
+	them will be guaranteed for at least 2 years.  Most interfaces
17
+	(like syscalls) are expected to never change and always be
18
+	available.
19
+
20
+  testing/
21
+	This directory documents interfaces that are felt to be stable,
22
+	as the main development of this interface has been completed.
23
+	The interface can be changed to add new features, but the
24
+	current interface will not break by doing this, unless grave
25
+	errors or security problems are found in them.  Userspace
26
+	programs can start to rely on these interfaces, but they must be
27
+	aware of changes that can occur before these interfaces move to
28
+	be marked stable.  Programs that use these interfaces are
29
+	strongly encouraged to add their name to the description of
30
+	these interfaces, so that the kernel developers can easily
31
+	notify them if any changes occur (see the description of the
32
+	layout of the files below for details on how to do this.)
33
+
34
+  obsolete/
35
+  	This directory documents interfaces that are still remaining in
36
+	the kernel, but are marked to be removed at some later point in
37
+	time.  The description of the interface will document the reason
38
+	why it is obsolete and when it can be expected to be removed.
39
+
40
+  removed/
41
+	This directory contains a list of the old interfaces that have
42
+	been removed from the kernel.
43
+
44
+Every file in these directories will contain the following information:
45
+
46
+What:		Short description of the interface
47
+Date:		Date created
48
+KernelVersion:	Kernel version this feature first showed up in.
49
+Contact:	Primary contact for this interface (may be a mailing list)
50
+Description:	Long description of the interface and how to use it.
51
+Users:		All users of this interface who wish to be notified when
52
+		it changes.  This is very important for interfaces in
53
+		the "testing" stage, so that kernel developers can work
54
+		with userspace developers to ensure that things do not
55
+		break in ways that are unacceptable.  It is also
56
+		important to get feedback for these interfaces to make
57
+		sure they are working in a proper way and do not need to
58
+		be changed further.
59
+
60
+
61
+How things move between levels:
62
+
63
+Interfaces in stable may move to obsolete, as long as the proper
64
+notification is given.
65
+
66
+Interfaces may be removed from obsolete and the kernel as long as the
67
+documented amount of time has gone by.
68
+
69
+Interfaces in the testing state can move to the stable state when the
70
+developers feel they are finished.  They cannot be removed from the
71
+kernel tree without going through the obsolete state first.
72
+
73
+It's up to the developer to place their interfaces in the category they
74
+wish for it to start out in.
75
+
76
+
77
+Notable bits of non-ABI, which should not under any circumstances be considered
78
+stable:
79
+
80
+- Kconfig.  Userspace should not rely on the presence or absence of any
81
+  particular Kconfig symbol, in /proc/config.gz, in the copy of .config
82
+  commonly installed to /boot, or in any invocation of the kernel build
83
+  process.
84
+
85
+- Kernel-internal symbols.  Do not rely on the presence, absence, location, or
86
+  type of any kernel symbol, either in System.map files or the kernel binary
87
+  itself.  See Documentation/stable_api_nonsense.txt.

+ 5 - 0
Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads

@@ -0,0 +1,5 @@
1
+What:		/proc/sys/vm/nr_pdflush_threads
2
+Date:		June 2012
3
+Contact:	Wanpeng Li <liwp@linux.vnet.ibm.com>
4
+Description: Since pdflush is replaced by per-BDI flusher, the interface of old pdflush
5
+             exported in /proc/sys/vm/ should be removed.

+ 119 - 0
Documentation/ABI/obsolete/sysfs-block-zram

@@ -0,0 +1,119 @@
1
+What:		/sys/block/zram<id>/num_reads
2
+Date:		August 2015
3
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
4
+Description:
5
+		The num_reads file is read-only and specifies the number of
6
+		reads (failed or successful) done on this device.
7
+		Now accessible via zram<id>/stat node.
8
+
9
+What:		/sys/block/zram<id>/num_writes
10
+Date:		August 2015
11
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
12
+Description:
13
+		The num_writes file is read-only and specifies the number of
14
+		writes (failed or successful) done on this device.
15
+		Now accessible via zram<id>/stat node.
16
+
17
+What:		/sys/block/zram<id>/invalid_io
18
+Date:		August 2015
19
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
20
+Description:
21
+		The invalid_io file is read-only and specifies the number of
22
+		non-page-size-aligned I/O requests issued to this device.
23
+		Now accessible via zram<id>/io_stat node.
24
+
25
+What:		/sys/block/zram<id>/failed_reads
26
+Date:		August 2015
27
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
28
+Description:
29
+		The failed_reads file is read-only and specifies the number of
30
+		failed reads happened on this device.
31
+		Now accessible via zram<id>/io_stat node.
32
+
33
+What:		/sys/block/zram<id>/failed_writes
34
+Date:		August 2015
35
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
36
+Description:
37
+		The failed_writes file is read-only and specifies the number of
38
+		failed writes happened on this device.
39
+		Now accessible via zram<id>/io_stat node.
40
+
41
+What:		/sys/block/zram<id>/notify_free
42
+Date:		August 2015
43
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
44
+Description:
45
+		The notify_free file is read-only. Depending on device usage
46
+		scenario it may account a) the number of pages freed because
47
+		of swap slot free notifications or b) the number of pages freed
48
+		because of REQ_DISCARD requests sent by bio. The former ones
49
+		are sent to a swap block device when a swap slot is freed, which
50
+		implies that this disk is being used as a swap disk. The latter
51
+		ones are sent by filesystem mounted with discard option,
52
+		whenever some data blocks are getting discarded.
53
+		Now accessible via zram<id>/io_stat node.
54
+
55
+What:		/sys/block/zram<id>/zero_pages
56
+Date:		August 2015
57
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
58
+Description:
59
+		The zero_pages file is read-only and specifies number of zero
60
+		filled pages written to this disk. No memory is allocated for
61
+		such pages.
62
+		Now accessible via zram<id>/mm_stat node.
63
+
64
+What:		/sys/block/zram<id>/orig_data_size
65
+Date:		August 2015
66
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
67
+Description:
68
+		The orig_data_size file is read-only and specifies uncompressed
69
+		size of data stored in this disk. This excludes zero-filled
70
+		pages (zero_pages) since no memory is allocated for them.
71
+		Unit: bytes
72
+		Now accessible via zram<id>/mm_stat node.
73
+
74
+What:		/sys/block/zram<id>/compr_data_size
75
+Date:		August 2015
76
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
77
+Description:
78
+		The compr_data_size file is read-only and specifies compressed
79
+		size of data stored in this disk. So, compression ratio can be
80
+		calculated using orig_data_size and this statistic.
81
+		Unit: bytes
82
+		Now accessible via zram<id>/mm_stat node.
83
+
84
+What:		/sys/block/zram<id>/mem_used_total
85
+Date:		August 2015
86
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
87
+Description:
88
+		The mem_used_total file is read-only and specifies the amount
89
+		of memory, including allocator fragmentation and metadata
90
+		overhead, allocated for this disk. So, allocator space
91
+		efficiency can be calculated using compr_data_size and this
92
+		statistic.
93
+		Unit: bytes
94
+		Now accessible via zram<id>/mm_stat node.
95
+
96
+What:		/sys/block/zram<id>/mem_used_max
97
+Date:		August 2015
98
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
99
+Description:
100
+		The mem_used_max file is read/write and specifies the amount
101
+		of maximum memory zram have consumed to store compressed data.
102
+		For resetting the value, you should write "0". Otherwise,
103
+		you could see -EINVAL.
104
+		Unit: bytes
105
+		Downgraded to write-only node: so it's possible to set new
106
+		value only; its current value is stored in zram<id>/mm_stat
107
+		node.
108
+
109
+What:		/sys/block/zram<id>/mem_limit
110
+Date:		August 2015
111
+Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
112
+Description:
113
+		The mem_limit file is read/write and specifies the maximum
114
+		amount of memory ZRAM can use to store the compressed data.
115
+		The limit could be changed in run time and "0" means disable
116
+		the limit.  No limit is the initial state.  Unit: bytes
117
+		Downgraded to write-only node: so it's possible to set new
118
+		value only; its current value is stored in zram<id>/mm_stat
119
+		node.

+ 31 - 0
Documentation/ABI/obsolete/sysfs-bus-usb

@@ -0,0 +1,31 @@
1
+What:		/sys/bus/usb/devices/.../power/level
2
+Date:		March 2007
3
+KernelVersion:	2.6.21
4
+Contact:	Alan Stern <stern@rowland.harvard.edu>
5
+Description:
6
+		Each USB device directory will contain a file named
7
+		power/level.  This file holds a power-level setting for
8
+		the device, either "on" or "auto".
9
+
10
+		"on" means that the device is not allowed to autosuspend,
11
+		although normal suspends for system sleep will still
12
+		be honored.  "auto" means the device will autosuspend
13
+		and autoresume in the usual manner, according to the
14
+		capabilities of its driver.
15
+
16
+		During normal use, devices should be left in the "auto"
17
+		level.  The "on" level is meant for administrative uses.
18
+		If you want to suspend a device immediately but leave it
19
+		free to wake up in response to I/O requests, you should
20
+		write "0" to power/autosuspend.
21
+
22
+		Device not capable of proper suspend and resume should be
23
+		left in the "on" level.  Although the USB spec requires
24
+		devices to support suspend/resume, many of them do not.
25
+		In fact so many don't that by default, the USB core
26
+		initializes all non-hub devices in the "on" level.  Some
27
+		drivers may change this setting when they are bound.
28
+
29
+		This file is deprecated and will be removed after 2010.
30
+		Use the power/control file instead; it does exactly the
31
+		same thing.

+ 29 - 0
Documentation/ABI/obsolete/sysfs-class-rfkill

@@ -0,0 +1,29 @@
1
+rfkill - radio frequency (RF) connector kill switch support
2
+
3
+For details to this subsystem look at Documentation/rfkill.txt.
4
+
5
+What:		/sys/class/rfkill/rfkill[0-9]+/state
6
+Date:		09-Jul-2007
7
+KernelVersion	v2.6.22
8
+Contact:	linux-wireless@vger.kernel.org
9
+Description: 	Current state of the transmitter.
10
+		This file is deprecated and scheduled to be removed in 2014,
11
+		because its not possible to express the 'soft and hard block'
12
+		state of the rfkill driver.
13
+Values: 	A numeric value.
14
+		0: RFKILL_STATE_SOFT_BLOCKED
15
+			transmitter is turned off by software
16
+		1: RFKILL_STATE_UNBLOCKED
17
+			transmitter is (potentially) active
18
+		2: RFKILL_STATE_HARD_BLOCKED
19
+			transmitter is forced off by something outside of
20
+			the driver's control.
21
+
22
+What:		/sys/class/rfkill/rfkill[0-9]+/claim
23
+Date:		09-Jul-2007
24
+KernelVersion	v2.6.22
25
+Contact:	linux-wireless@vger.kernel.org
26
+Description:	This file is deprecated because there no longer is a way to
27
+		claim just control over a single rfkill instance.
28
+		This file is scheduled to be removed in 2012.
29
+Values: 	0: Kernel handles events

+ 53 - 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo

@@ -0,0 +1,53 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/actual_profile
2
+Date:		Januar 2011
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The integer value of this attribute ranges from 1-5.
5
+		When read, this attribute returns the number of the actual
6
+		profile which is also the profile that's active on device startup.
7
+		When written this attribute activates the selected profile
8
+		immediately.
9
+Users:		http://roccat.sourceforge.net
10
+
11
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/button
12
+Date:		Januar 2011
13
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
14
+Description:	The keyboard can store short macros with consist of 1 button with
15
+		several modifier keys internally.
16
+		When written, this file lets one set the sequence for a specific
17
+		button for a specific profile. Button and profile numbers are
18
+		included in written data. The data has to be 24 bytes long.
19
+		This file is writeonly.
20
+Users:		http://roccat.sourceforge.net
21
+
22
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/info
23
+Date:		Januar 2011
24
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
25
+Description:	When read, this file returns some info about the device like the
26
+		installed firmware version.
27
+		The size of the data is 8 bytes in size.
28
+		This file is readonly.
29
+Users:		http://roccat.sourceforge.net
30
+
31
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/key_mask
32
+Date:		Januar 2011
33
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
34
+Description:	The keyboard lets the user deactivate 5 certain keys like the
35
+		windows and application keys, to protect the user from the outcome
36
+		of accidentally pressing them.
37
+		The integer value of this attribute has bits 0-4 set depending
38
+		on the state of the corresponding key.
39
+		When read, this file returns the current state of the buttons.
40
+		When written, the given buttons are activated/deactivated
41
+		immediately.
42
+Users:		http://roccat.sourceforge.net
43
+
44
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/arvo/roccatarvo<minor>/mode_key
45
+Date:		Januar 2011
46
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
47
+Description:	The keyboard has a condensed layout without num-lock key.
48
+		Instead it uses a mode-key which activates a gaming mode where
49
+		the assignment of the number block changes.
50
+		The integer value of this attribute ranges from 0 (OFF) to 1 (ON).
51
+		When read, this file returns the actual state of the key.
52
+		When written, the key is activated/deactivated immediately.
53
+Users:		http://roccat.sourceforge.net

+ 153 - 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku

@@ -0,0 +1,153 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/actual_profile
2
+Date:		June 2011
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The integer value of this attribute ranges from 0-4.
5
+		When read, this attribute returns the number of the actual
6
+		profile. This value is persistent, so its equivalent to the
7
+		profile that's active when the device is powered on next time.
8
+		When written, this file sets the number of the startup profile
9
+		and the device activates this profile immediately.
10
+Users:		http://roccat.sourceforge.net
11
+
12
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/info
13
+Date:		June 2011
14
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
15
+Description:	When read, this file returns general data like firmware version.
16
+		The data is 6 bytes long.
17
+		This file is readonly.
18
+Users:		http://roccat.sourceforge.net
19
+
20
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/key_mask
21
+Date:		June 2011
22
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
23
+Description:	When written, this file lets one deactivate certain keys like
24
+		windows and application keys, to prevent accidental presses.
25
+		Profile number for which this settings occur is included in
26
+		written data. The data has to be 6 bytes long.
27
+		Before reading this file, control has to be written to select
28
+		which profile to read.
29
+Users:		http://roccat.sourceforge.net
30
+
31
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_capslock
32
+Date:		June 2011
33
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
34
+Description:	When written, this file lets one set the function of the
35
+		capslock key for a specific profile. Profile number is included
36
+		in written data. The data has to be 6 bytes long.
37
+		Before reading this file, control has to be written to select
38
+		which profile to read.
39
+Users:		http://roccat.sourceforge.net
40
+
41
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_easyzone
42
+Date:		June 2011
43
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
44
+Description:	When written, this file lets one set the function of the
45
+		easyzone keys for a specific profile. Profile number is included
46
+		in written data. The data has to be 65 bytes long.
47
+		Before reading this file, control has to be written to select
48
+		which profile to read.
49
+Users:		http://roccat.sourceforge.net
50
+
51
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_function
52
+Date:		June 2011
53
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
54
+Description:	When written, this file lets one set the function of the
55
+		function keys for a specific profile. Profile number is included
56
+		in written data. The data has to be 41 bytes long.
57
+		Before reading this file, control has to be written to select
58
+		which profile to read.
59
+Users:		http://roccat.sourceforge.net
60
+
61
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_macro
62
+Date:		June 2011
63
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
64
+Description:	When written, this file lets one set the function of the macro
65
+		keys for a specific profile. Profile number is included in
66
+		written data. The data has to be 35 bytes long.
67
+		Before reading this file, control has to be written to select
68
+		which profile to read.
69
+Users:		http://roccat.sourceforge.net
70
+
71
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_media
72
+Date:		June 2011
73
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
74
+Description:	When written, this file lets one set the function of the media
75
+		keys for a specific profile. Profile number is included in
76
+		written data. The data has to be 29 bytes long.
77
+		Before reading this file, control has to be written to select
78
+		which profile to read.
79
+Users:		http://roccat.sourceforge.net
80
+
81
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/keys_thumbster
82
+Date:		June 2011
83
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
84
+Description:	When written, this file lets one set the function of the
85
+		thumbster keys for a specific profile. Profile number is included
86
+		in written data. The data has to be 23 bytes long.
87
+		Before reading this file, control has to be written to select
88
+		which profile to read.
89
+Users:		http://roccat.sourceforge.net
90
+
91
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/last_set
92
+Date:		June 2011
93
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
94
+Description:	When written, this file lets one set the time in secs since
95
+		epoch in which the last configuration took place.
96
+		The data has to be 20 bytes long.
97
+Users:		http://roccat.sourceforge.net
98
+
99
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/light
100
+Date:		June 2011
101
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
102
+Description:	When written, this file lets one set the backlight intensity for
103
+		a specific profile. Profile number is included in written data.
104
+		The data has to be 10 bytes long for Isku, IskuFX needs	16 bytes
105
+		of data.
106
+		Before reading this file, control has to be written to select
107
+		which profile to read.
108
+Users:		http://roccat.sourceforge.net
109
+
110
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/macro
111
+Date:		June 2011
112
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
113
+Description:	When written, this file lets one store macros with max 500
114
+		keystrokes for a specific button for a specific profile.
115
+		Button and profile numbers are included in written data.
116
+		The data has to be 2083 bytes long.
117
+		Before reading this file, control has to be written to select
118
+		which profile and key to read.
119
+Users:		http://roccat.sourceforge.net
120
+
121
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/reset
122
+Date:		November 2012
123
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
124
+Description:	When written, this file lets one reset the device.
125
+		The data has to be 3 bytes long.
126
+		This file is writeonly.
127
+Users:		http://roccat.sourceforge.net
128
+
129
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/control
130
+Date:		June 2011
131
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
132
+Description:	When written, this file lets one select which data from which
133
+		profile will be	read next. The data has to be 3 bytes long.
134
+		This file is writeonly.
135
+Users:		http://roccat.sourceforge.net
136
+
137
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/talk
138
+Date:		June 2011
139
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
140
+Description:	When written, this file lets one trigger easyshift functionality
141
+		from the host.
142
+		The data has to be 16 bytes long.
143
+		This file is writeonly.
144
+Users:		http://roccat.sourceforge.net
145
+
146
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/isku/roccatisku<minor>/talkfx
147
+Date:		February 2013
148
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
149
+Description:	When written, this file lets one trigger temporary color schemes
150
+		from the host.
151
+		The data has to be 16 bytes long.
152
+		This file is writeonly.
153
+Users:		http://roccat.sourceforge.net

+ 145 - 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus

@@ -0,0 +1,145 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/actual_profile
2
+Date:		October 2010
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The integer value of this attribute ranges from 0-4.
5
+                When read, this attribute returns the number of the actual
6
+                profile. This value is persistent, so its equivalent to the
7
+                profile that's active when the mouse is powered on next time.
8
+		When written, this file sets the number of the startup profile
9
+		and the mouse activates this profile immediately.
10
+Users:		http://roccat.sourceforge.net
11
+
12
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/startup_profile
13
+Date:		October 2010
14
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
15
+Description:	The integer value of this attribute ranges from 0-4.
16
+                When read, this attribute returns the number of the actual
17
+                profile. This value is persistent, so its equivalent to the
18
+                profile that's active when the mouse is powered on next time.
19
+		When written, this file sets the number of the startup profile
20
+		and the mouse activates this profile immediately.
21
+		Please use actual_profile, it does the same thing.
22
+Users:		http://roccat.sourceforge.net
23
+
24
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/firmware_version
25
+Date:		October 2010
26
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
27
+Description:	When read, this file returns the raw integer version number of the
28
+		firmware reported by the mouse. Using the integer value eases
29
+		further usage in other programs. To receive the real version
30
+		number the decimal point has to be shifted 2 positions to the
31
+		left. E.g. a returned value of 121 means 1.21
32
+		This file is readonly.
33
+		Please read binary attribute info which contains firmware version.
34
+Users:		http://roccat.sourceforge.net
35
+
36
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/info
37
+Date:		November 2012
38
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
39
+Description:	When read, this file returns general data like firmware version.
40
+		When written, the device can be reset.
41
+		The data is 8 bytes long.
42
+Users:		http://roccat.sourceforge.net
43
+
44
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/macro
45
+Date:		October 2010
46
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
47
+Description:	The mouse can store a macro with max 500 key/button strokes
48
+		internally.
49
+		When written, this file lets one set the sequence for a specific
50
+		button for a specific profile. Button and profile numbers are
51
+		included in written data. The data has to be 2082 bytes long.
52
+		This file is writeonly.
53
+Users:		http://roccat.sourceforge.net
54
+
55
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile_buttons
56
+Date:		August 2010
57
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
58
+Description:	The mouse can store 5 profiles which can be switched by the
59
+		press of a button. A profile is split in settings and buttons.
60
+		profile_buttons holds information about button layout.
61
+		When written, this file lets one write the respective profile
62
+		buttons back to the mouse. The data has to be 77 bytes long.
63
+		The mouse will reject invalid data.
64
+		Which profile to write is determined by the profile number
65
+		contained in the data.
66
+		Before reading this file, control has to be written to select
67
+		which profile to read.
68
+Users:		http://roccat.sourceforge.net
69
+
70
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile[1-5]_buttons
71
+Date:		August 2010
72
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
73
+Description:	The mouse can store 5 profiles which can be switched by the
74
+		press of a button. A profile is split in settings and buttons.
75
+		profile_buttons holds information about button layout.
76
+		When read, these files return the respective profile buttons.
77
+		The returned data is 77 bytes in size.
78
+		This file is readonly.
79
+		Write control to select profile and read profile_buttons instead.
80
+Users:		http://roccat.sourceforge.net
81
+
82
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile_settings
83
+Date:		October 2010
84
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
85
+Description:	The mouse can store 5 profiles which can be switched by the
86
+		press of a button. A profile is split in settings and buttons.
87
+		profile_settings holds information like resolution, sensitivity
88
+		and light effects.
89
+		When written, this file lets one write the respective profile
90
+		settings back to the mouse. The data has to be 43 bytes long.
91
+		The mouse will reject invalid data.
92
+		Which profile to write is determined by the profile number
93
+		contained in the data.
94
+		Before reading this file, control has to be written to select
95
+		which profile to read.
96
+Users:		http://roccat.sourceforge.net
97
+
98
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile[1-5]_settings
99
+Date:		August 2010
100
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
101
+Description:	The mouse can store 5 profiles which can be switched by the
102
+		press of a button. A profile is split in settings and buttons.
103
+		profile_settings holds information like resolution, sensitivity
104
+		and light effects.
105
+		When read, these files return the respective profile settings.
106
+		The returned data is 43 bytes in size.
107
+		This file is readonly.
108
+		Write control to select profile and read profile_settings instead.
109
+Users:		http://roccat.sourceforge.net
110
+
111
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/sensor
112
+Date:		October 2010
113
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
114
+Description:	The mouse has a tracking- and a distance-control-unit. These
115
+		can be activated/deactivated and the lift-off distance can be
116
+		set. The data has to be 6 bytes long.
117
+		This file is writeonly.
118
+Users:		http://roccat.sourceforge.net
119
+
120
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/talk
121
+Date:		May 2011
122
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
123
+Description:	Used to active some easy* functions of the mouse from outside.
124
+		The data has to be 16 bytes long.
125
+		This file is writeonly.
126
+Users:		http://roccat.sourceforge.net
127
+
128
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/tcu
129
+Date:		October 2010
130
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
131
+Description:	When written a calibration process for the tracking control unit
132
+		can be initiated/cancelled. Also lets one read/write sensor
133
+		registers.
134
+		The data has to be 4 bytes long.
135
+Users:		http://roccat.sourceforge.net
136
+
137
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/tcu_image
138
+Date:		October 2010
139
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
140
+Description:	When read the mouse returns a 30x30 pixel image of the
141
+		sampled underground. This works only in the course of a
142
+		calibration process initiated with tcu.
143
+		The returned data is 1028 bytes in size.
144
+		This file is readonly.
145
+Users:		http://roccat.sourceforge.net

+ 105 - 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure

@@ -0,0 +1,105 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/actual_profile
2
+Date:		December 2012
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The mouse can store 5 profiles which can be switched by the
5
+		press of a button. actual_profile holds number of actual profile.
6
+		This value is persistent, so its value determines the profile
7
+		that's active when the mouse is powered on next time.
8
+		When written, the mouse activates the set profile immediately.
9
+		The data has to be 3 bytes long.
10
+		The mouse will reject invalid data.
11
+Users:		http://roccat.sourceforge.net
12
+
13
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/control
14
+Date:		December 2012
15
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
16
+Description:	When written, this file lets one select which data from which
17
+		profile will be	read next. The data has to be 3 bytes long.
18
+		This file is writeonly.
19
+Users:		http://roccat.sourceforge.net
20
+
21
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/info
22
+Date:		December 2012
23
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
24
+Description:	When read, this file returns general data like firmware version.
25
+		When written, the device can be reset.
26
+		The data is 6 bytes long.
27
+Users:		http://roccat.sourceforge.net
28
+
29
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/macro
30
+Date:		December 2012
31
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
32
+Description:	The mouse can store a macro with max 500 key/button strokes
33
+		internally.
34
+		When written, this file lets one set the sequence for a specific
35
+		button for a specific profile. Button and profile numbers are
36
+		included in written data. The data has to be 2082 bytes long.
37
+		This file is writeonly.
38
+Users:		http://roccat.sourceforge.net
39
+
40
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/profile_buttons
41
+Date:		December 2012
42
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
43
+Description:	The mouse can store 5 profiles which can be switched by the
44
+		press of a button. A profile is split in settings and buttons.
45
+		profile_buttons holds information about button layout.
46
+		When written, this file lets one write the respective profile
47
+		buttons back to the mouse. The data has to be 59 bytes long.
48
+		The mouse will reject invalid data.
49
+		Which profile to write is determined by the profile number
50
+		contained in the data.
51
+		Before reading this file, control has to be written to select
52
+		which profile to read.
53
+Users:		http://roccat.sourceforge.net
54
+
55
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/profile_settings
56
+Date:		December 2012
57
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
58
+Description:	The mouse can store 5 profiles which can be switched by the
59
+		press of a button. A profile is split in settings and buttons.
60
+		profile_settings holds information like resolution, sensitivity
61
+		and light effects.
62
+		When written, this file lets one write the respective profile
63
+		settings back to the mouse. The data has to be 31 bytes long.
64
+		The mouse will reject invalid data.
65
+		Which profile to write is determined by the profile number
66
+		contained in the data.
67
+		Before reading this file, control has to be written to select
68
+		which profile to read.
69
+Users:		http://roccat.sourceforge.net
70
+
71
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/sensor
72
+Date:		December 2012
73
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
74
+Description:	The mouse has a tracking- and a distance-control-unit. These
75
+		can be activated/deactivated and the lift-off distance can be
76
+		set. The data has to be 6 bytes long.
77
+		This file is writeonly.
78
+Users:		http://roccat.sourceforge.net
79
+
80
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/talk
81
+Date:		December 2012
82
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
83
+Description:	Used to active some easy* functions of the mouse from outside.
84
+		The data has to be 16 bytes long.
85
+		This file is writeonly.
86
+Users:		http://roccat.sourceforge.net
87
+
88
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/tcu
89
+Date:		December 2012
90
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
91
+Description:	When written a calibration process for the tracking control unit
92
+		can be initiated/cancelled. Also lets one read/write sensor
93
+		registers.
94
+		The data has to be 4 bytes long.
95
+Users:		http://roccat.sourceforge.net
96
+
97
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/konepure/roccatkonepure<minor>/tcu_image
98
+Date:		December 2012
99
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
100
+Description:	When read the mouse returns a 30x30 pixel image of the
101
+		sampled underground. This works only in the course of a
102
+		calibration process initiated with tcu.
103
+		The returned data is 1028 bytes in size.
104
+		This file is readonly.
105
+Users:		http://roccat.sourceforge.net

+ 116 - 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus

@@ -0,0 +1,116 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_cpi
2
+Date:		January 2011
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The integer value of this attribute ranges from 1-4.
5
+		When read, this attribute returns the number of the active
6
+		cpi level.
7
+		This file is readonly.
8
+		Has never been used. If bookkeeping is done, it's done in userland tools.
9
+Users:		http://roccat.sourceforge.net
10
+
11
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_profile
12
+Date:		January 2011
13
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
14
+Description:	The integer value of this attribute ranges from 0-4.
15
+		When read, this attribute returns the number of the active
16
+		profile.
17
+		When written, the mouse activates this profile immediately.
18
+		The profile that's active when powered down is the same that's
19
+		active when the mouse is powered on.
20
+Users:		http://roccat.sourceforge.net
21
+
22
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_x
23
+Date:		January 2011
24
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
25
+Description:	The integer value of this attribute ranges from 1-10.
26
+		When read, this attribute returns the number of the actual
27
+		sensitivity in x direction.
28
+		This file is readonly.
29
+		Has never been used. If bookkeeping is done, it's done in userland tools.
30
+Users:		http://roccat.sourceforge.net
31
+
32
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_y
33
+Date:		January 2011
34
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
35
+Description:	The integer value of this attribute ranges from 1-10.
36
+		When read, this attribute returns the number of the actual
37
+		sensitivity in y direction.
38
+		This file is readonly.
39
+		Has never been used. If bookkeeping is done, it's done in userland tools.
40
+Users:		http://roccat.sourceforge.net
41
+
42
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/firmware_version
43
+Date:		January 2011
44
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
45
+Description:	When read, this file returns the raw integer version number of the
46
+		firmware reported by the mouse. Using the integer value eases
47
+		further usage in other programs. To receive the real version
48
+		number the decimal point has to be shifted 2 positions to the
49
+		left. E.g. a returned value of 121 means 1.21
50
+		This file is readonly.
51
+		Obsoleted by binary sysfs attribute "info".
52
+Users:		http://roccat.sourceforge.net
53
+
54
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/info
55
+Date:		November 2012
56
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
57
+Description:	When read, this file returns general data like firmware version.
58
+		When written, the device can be reset.
59
+		The data is 6 bytes long.
60
+Users:		http://roccat.sourceforge.net
61
+
62
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile_buttons
63
+Date:		January 2011
64
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
65
+Description:	The mouse can store 5 profiles which can be switched by the
66
+		press of a button. A profile is split in settings and buttons.
67
+		profile_buttons holds information about button layout.
68
+		When written, this file lets one write the respective profile
69
+		buttons back to the mouse. The data has to be 23 bytes long.
70
+		The mouse will reject invalid data.
71
+		Which profile to write is determined by the profile number
72
+		contained in the data.
73
+		Before reading this file, control has to be written to select
74
+		which profile to read.
75
+Users:		http://roccat.sourceforge.net
76
+
77
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile[1-5]_buttons
78
+Date:		January 2011
79
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
80
+Description:	The mouse can store 5 profiles which can be switched by the
81
+		press of a button. A profile is split in settings and buttons.
82
+		profile_buttons holds information about button layout.
83
+		When read, these files return the respective profile buttons.
84
+		The returned data is 23 bytes in size.
85
+		This file is readonly.
86
+		Write control to select profile and read profile_buttons instead.
87
+Users:		http://roccat.sourceforge.net
88
+
89
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile_settings
90
+Date:		January 2011
91
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
92
+Description:	The mouse can store 5 profiles which can be switched by the
93
+		press of a button. A profile is split in settings and buttons.
94
+		profile_settings holds information like resolution, sensitivity
95
+		and light effects.
96
+		When written, this file lets one write the respective profile
97
+		settings back to the mouse. The data has to be 16 bytes long.
98
+		The mouse will reject invalid data.
99
+		Which profile to write is determined by the profile number
100
+		contained in the data.
101
+		Before reading this file, control has to be written to select
102
+		which profile to read.
103
+Users:		http://roccat.sourceforge.net
104
+
105
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile[1-5]_settings
106
+Date:		January 2011
107
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
108
+Description:	The mouse can store 5 profiles which can be switched by the
109
+		press of a button. A profile is split in settings and buttons.
110
+		profile_settings holds information like resolution, sensitivity
111
+		and light effects.
112
+		When read, these files return the respective profile settings.
113
+		The returned data is 16 bytes in size.
114
+		This file is readonly.
115
+		Write control to select profile and read profile_settings instead.
116
+Users:		http://roccat.sourceforge.net

+ 7 - 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua

@@ -0,0 +1,7 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/control
2
+Date:		October 2012
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	When written, cpi, button and light settings can be configured.
5
+		When read, actual cpi setting and sensor data are returned.
6
+		The data has to be 8 bytes long.
7
+Users:		http://roccat.sourceforge.net

+ 123 - 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra

@@ -0,0 +1,123 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/actual_cpi
2
+Date:		August 2010
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	It is possible to switch the cpi setting of the mouse with the
5
+		press of a button.
6
+		When read, this file returns the raw number of the actual cpi
7
+		setting reported by the mouse. This number has to be further
8
+		processed to receive the real dpi value.
9
+
10
+		VALUE DPI
11
+		1     400
12
+		2     800
13
+		4     1600
14
+
15
+		This file is readonly.
16
+		Has never been used. If bookkeeping is done, it's done in userland tools.
17
+Users:		http://roccat.sourceforge.net
18
+
19
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/actual_profile
20
+Date:		August 2010
21
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
22
+Description:	When read, this file returns the number of the actual profile in
23
+		range 0-4.
24
+		This file is readonly.
25
+		Please use binary attribute "settings" which provides this information.
26
+Users:		http://roccat.sourceforge.net
27
+
28
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/firmware_version
29
+Date:		August 2010
30
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
31
+Description:	When read, this file returns the raw integer version number of the
32
+		firmware reported by the mouse. Using the integer value eases
33
+		further usage in other programs. To receive the real version
34
+		number the decimal point has to be shifted 2 positions to the
35
+		left. E.g. a returned value of 138 means 1.38
36
+		This file is readonly.
37
+		Please use binary attribute "info" which provides this information.
38
+Users:		http://roccat.sourceforge.net
39
+
40
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/info
41
+Date:		November 2012
42
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
43
+Description:	When read, this file returns general data like firmware version.
44
+		When written, the device can be reset.
45
+		The data is 6 bytes long.
46
+Users:		http://roccat.sourceforge.net
47
+
48
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile_buttons
49
+Date:		August 2010
50
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
51
+Description:	The mouse can store 5 profiles which can be switched by the
52
+		press of a button. A profile is split in settings and buttons.
53
+		profile_buttons holds information about button layout.
54
+		When written, this file lets one write the respective profile
55
+		buttons back to the mouse. The data has to be 19 bytes long.
56
+		The mouse will reject invalid data.
57
+		Which profile to write is determined by the profile number
58
+		contained in the data.
59
+		Before reading this file, control has to be written to select
60
+		which profile to read.
61
+Users:		http://roccat.sourceforge.net
62
+
63
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile[1-5]_buttons
64
+Date:		August 2010
65
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
66
+Description:	The mouse can store 5 profiles which can be switched by the
67
+		press of a button. A profile is split in settings and buttons.
68
+		profile_buttons holds information about button layout.
69
+		When read, these files return the respective profile buttons.
70
+		The returned data is 19 bytes in size.
71
+		This file is readonly.
72
+		Write control to select profile and read profile_buttons instead.
73
+Users:		http://roccat.sourceforge.net
74
+
75
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile_settings
76
+Date:		August 2010
77
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
78
+Description:	The mouse can store 5 profiles which can be switched by the
79
+		press of a button. A profile is split in settings and buttons.
80
+		profile_settings holds information like resolution, sensitivity
81
+		and light effects.
82
+		When written, this file lets one write the respective profile
83
+		settings back to the mouse. The data has to be 13 bytes long.
84
+		The mouse will reject invalid data.
85
+		Which profile to write is determined by the profile number
86
+		contained in the data.
87
+		Before reading this file, control has to be written to select
88
+		which profile to read.
89
+Users:		http://roccat.sourceforge.net
90
+
91
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile[1-5]_settings
92
+Date:		August 2010
93
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
94
+Description:	The mouse can store 5 profiles which can be switched by the
95
+		press of a button. A profile is split in settings and buttons.
96
+		profile_settings holds information like resolution, sensitivity
97
+		and light effects.
98
+		When read, these files return the respective profile settings.
99
+		The returned data is 13 bytes in size.
100
+		This file is readonly.
101
+		Write control to select profile and read profile_settings instead.
102
+Users:		http://roccat.sourceforge.net
103
+
104
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/settings
105
+Date:		August 2010
106
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
107
+Description:	When read, this file returns the settings stored in the mouse.
108
+		The size of the data is 3 bytes and holds information on the
109
+		startup_profile.
110
+		When written, this file lets write settings back to the mouse.
111
+		The data has to be 3 bytes long. The mouse will reject invalid
112
+		data.
113
+Users:		http://roccat.sourceforge.net
114
+
115
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/startup_profile
116
+Date:		August 2010
117
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
118
+Description:	The integer value of this attribute ranges from 0-4.
119
+                When read, this attribute returns the number of the profile
120
+                that's active when the mouse is powered on.
121
+		This file is readonly.
122
+		Please use binary attribute "settings" which provides this information.
123
+Users:		http://roccat.sourceforge.net

+ 178 - 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos

@@ -0,0 +1,178 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/control
2
+Date:		October 2013
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	When written, this file lets one select which data from which
5
+		profile will be	read next. The data has to be 3 bytes long.
6
+		This file is writeonly.
7
+Users:		http://roccat.sourceforge.net
8
+
9
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/profile
10
+Date:		October 2013
11
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
12
+Description:	The mouse can store 5 profiles which can be switched by the
13
+		press of a button. profile holds index of actual profile.
14
+		This value is persistent, so its value determines the profile
15
+		that's active when the device is powered on next time.
16
+		When written, the device activates the set profile immediately.
17
+		The data has to be 3 bytes long.
18
+		The device will reject invalid data.
19
+Users:		http://roccat.sourceforge.net
20
+
21
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_primary
22
+Date:		October 2013
23
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
24
+Description:	When written, this file lets one set the default of all keys for
25
+		a specific profile. Profile index is included in written data.
26
+		The data has to be 125 bytes long.
27
+		Before reading this file, control has to be written to select
28
+		which profile to read.
29
+Users:		http://roccat.sourceforge.net
30
+
31
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_function
32
+Date:		October 2013
33
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
34
+Description:	When written, this file lets one set the function of the
35
+		function keys for a specific profile. Profile index is included
36
+		in written data. The data has to be 95 bytes long.
37
+		Before reading this file, control has to be written to select
38
+		which profile to read.
39
+Users:		http://roccat.sourceforge.net
40
+
41
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_macro
42
+Date:		October 2013
43
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
44
+Description:	When written, this file lets one set the function of the macro
45
+		keys for a specific profile. Profile index is included in
46
+		written data. The data has to be 35 bytes long.
47
+		Before reading this file, control has to be written to select
48
+		which profile to read.
49
+Users:		http://roccat.sourceforge.net
50
+
51
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_thumbster
52
+Date:		October 2013
53
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
54
+Description:	When written, this file lets one set the function of the
55
+		thumbster keys for a specific profile. Profile index is included
56
+		in written data. The data has to be 23 bytes long.
57
+		Before reading this file, control has to be written to select
58
+		which profile to read.
59
+Users:		http://roccat.sourceforge.net
60
+
61
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_extra
62
+Date:		October 2013
63
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
64
+Description:	When written, this file lets one set the function of the
65
+		capslock and function keys for a specific profile. Profile index
66
+		is included in written data. The data has to be 8 bytes long.
67
+		Before reading this file, control has to be written to select
68
+		which profile to read.
69
+Users:		http://roccat.sourceforge.net
70
+
71
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/keys_easyzone
72
+Date:		October 2013
73
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
74
+Description:	When written, this file lets one set the function of the
75
+		easyzone keys for a specific profile. Profile index is included
76
+		in written data. The data has to be 294 bytes long.
77
+		Before reading this file, control has to be written to select
78
+		which profile to read.
79
+Users:		http://roccat.sourceforge.net
80
+
81
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/key_mask
82
+Date:		October 2013
83
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
84
+Description:	When written, this file lets one deactivate certain keys like
85
+		windows and application keys, to prevent accidental presses.
86
+		Profile index for which this settings occur is included in
87
+		written data. The data has to be 6 bytes long.
88
+		Before reading this file, control has to be written to select
89
+		which profile to read.
90
+Users:		http://roccat.sourceforge.net
91
+
92
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/light
93
+Date:		October 2013
94
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
95
+Description:	When written, this file lets one set the backlight intensity for
96
+		a specific profile. Profile index is included in written data.
97
+		This attribute is only valid for the glow and pro variant.
98
+		The data has to be 16 bytes long.
99
+		Before reading this file, control has to be written to select
100
+		which profile to read.
101
+Users:		http://roccat.sourceforge.net
102
+
103
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/macro
104
+Date:		October 2013
105
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
106
+Description:	When written, this file lets one store macros with max 480
107
+		keystrokes for a specific button for a specific profile.
108
+		Button and profile indexes are included in written data.
109
+		The data has to be 2002 bytes long.
110
+		Before reading this file, control has to be written to select
111
+		which profile and key to read.
112
+Users:		http://roccat.sourceforge.net
113
+
114
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/info
115
+Date:		October 2013
116
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
117
+Description:	When read, this file returns general data like firmware version.
118
+		The data is 8 bytes long.
119
+		This file is readonly.
120
+Users:		http://roccat.sourceforge.net
121
+
122
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/reset
123
+Date:		October 2013
124
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
125
+Description:	When written, this file lets one reset the device.
126
+		The data has to be 3 bytes long.
127
+		This file is writeonly.
128
+Users:		http://roccat.sourceforge.net
129
+
130
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/talk
131
+Date:		October 2013
132
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
133
+Description:	When written, this file lets one trigger easyshift functionality
134
+		from the host.
135
+		The data has to be 16 bytes long.
136
+		This file is writeonly.
137
+Users:		http://roccat.sourceforge.net
138
+
139
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/light_control
140
+Date:		October 2013
141
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
142
+Description:	When written, this file lets one switch between stored and custom
143
+		light settings.
144
+		This attribute is only valid for the pro variant.
145
+		The data has to be 8 bytes long.
146
+		This file is writeonly.
147
+Users:		http://roccat.sourceforge.net
148
+
149
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/stored_lights
150
+Date:		October 2013
151
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
152
+Description:	When written, this file lets one set per-key lighting for different
153
+		layers.
154
+		This attribute is only valid for the pro variant.
155
+		The data has to be 1382 bytes long.
156
+		Before reading this file, control has to be written to select
157
+		which profile to read.
158
+Users:		http://roccat.sourceforge.net
159
+
160
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/custom_lights
161
+Date:		October 2013
162
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
163
+Description:	When written, this file lets one set the actual per-key lighting.
164
+		This attribute is only valid for the pro variant.
165
+		The data has to be 20 bytes long.
166
+		This file is writeonly.
167
+Users:		http://roccat.sourceforge.net
168
+
169
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/ryos/roccatryos<minor>/light_macro
170
+Date:		October 2013
171
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
172
+Description:	When written, this file lets one set a light macro that is looped
173
+		whenever the device gets in dimness mode.
174
+		This attribute is only valid for the pro variant.
175
+		The data has to be 2002 bytes long.
176
+		Before reading this file, control has to be written to select
177
+		which profile to read.
178
+Users:		http://roccat.sourceforge.net

+ 76 - 0
Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu

@@ -0,0 +1,76 @@
1
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/buttons
2
+Date:		Mai 2012
3
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
4
+Description:	The mouse can store 5 profiles which can be switched by the
5
+		press of a button. A profile is split into general settings and
6
+		button settings. buttons holds informations about button layout.
7
+		When written, this file lets one write the respective profile
8
+		buttons to the mouse. The data has to be 47 bytes long.
9
+		The mouse will reject invalid data.
10
+		Which profile to write is determined by the profile number
11
+		contained in the data.
12
+		Before reading this file, control has to be written to select
13
+		which profile to read.
14
+Users:		http://roccat.sourceforge.net
15
+
16
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/control
17
+Date:		Mai 2012
18
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
19
+Description:	When written, this file lets one select which data from which
20
+		profile will be	read next. The data has to be 3 bytes long.
21
+		This file is writeonly.
22
+Users:		http://roccat.sourceforge.net
23
+
24
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/general
25
+Date:		Mai 2012
26
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
27
+Description:	The mouse can store 5 profiles which can be switched by the
28
+		press of a button. A profile is split into general settings and
29
+		button settings. profile holds informations like resolution, sensitivity
30
+		and light effects.
31
+		When written, this file lets one write the respective profile
32
+		settings back to the mouse. The data has to be 43 bytes long.
33
+		The mouse will reject invalid data.
34
+		Which profile to write is determined by the profile number
35
+		contained in the data.
36
+		This file is writeonly.
37
+Users:		http://roccat.sourceforge.net
38
+
39
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/info
40
+Date:		Mai 2012
41
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
42
+Description:	When read, this file returns general data like firmware version.
43
+		When written, the device can be reset.
44
+		The data is 8 bytes long.
45
+Users:		http://roccat.sourceforge.net
46
+
47
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/macro
48
+Date:		Mai 2012
49
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
50
+Description:	When written, this file lets one store macros with max 500
51
+		keystrokes for a specific button for a specific profile.
52
+		Button and profile numbers are included in written data.
53
+		The data has to be 2083 bytes long.
54
+		Before reading this file, control has to be written to select
55
+		which profile and key to read.
56
+Users:		http://roccat.sourceforge.net
57
+
58
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/profile
59
+Date:		Mai 2012
60
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
61
+Description:	The mouse can store 5 profiles which can be switched by the
62
+		press of a button. profile holds number of actual profile.
63
+		This value is persistent, so its value determines the profile
64
+		that's active when the mouse is powered on next time.
65
+		When written, the mouse activates the set profile immediately.
66
+		The data has to be 3 bytes long.
67
+		The mouse will reject invalid data.
68
+Users:		http://roccat.sourceforge.net
69
+
70
+What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/savu/roccatsavu<minor>/sensor
71
+Date:		July 2012
72
+Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
73
+Description:	The mouse has a Avago ADNS-3090 sensor.
74
+		This file allows reading and writing of the mouse sensors registers.
75
+		The data has to be 4 bytes long.
76
+Users:		http://roccat.sourceforge.net

+ 12 - 0
Documentation/ABI/removed/devfs

@@ -0,0 +1,12 @@
1
+What:		devfs
2
+Date:		July 2005 (scheduled), finally removed in kernel v2.6.18
3
+Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
4
+Description:
5
+	devfs has been unmaintained for a number of years, has unfixable
6
+	races, contains a naming policy within the kernel that is
7
+	against the LSB, and can be replaced by using udev.
8
+	The files fs/devfs/*, include/linux/devfs_fs*.h were removed,
9
+	along with the assorted devfs function calls throughout the
10
+	kernel tree.
11
+
12
+Users:

+ 14 - 0
Documentation/ABI/removed/dv1394

@@ -0,0 +1,14 @@
1
+What:		dv1394 (a.k.a. "OHCI-DV I/O support" for FireWire)
2
+Date:		May 2010 (scheduled), finally removed in kernel v2.6.37
3
+Contact:	linux1394-devel@lists.sourceforge.net
4
+Description:
5
+	/dev/dv1394/* were character device files, one for each FireWire
6
+	controller and for NTSC and PAL respectively, from which DV data
7
+	could be received by read() or transmitted by write().  A few
8
+	ioctl()s allowed limited control.
9
+	This special-purpose interface has been superseded by libraw1394 +
10
+	libiec61883 which are functionally equivalent, support HDV, and
11
+	transparently work on top of the newer firewire kernel drivers.
12
+
13
+Users:
14
+	ffmpeg/libavformat (if configured for DV1394)

+ 9 - 0
Documentation/ABI/removed/ip_queue

@@ -0,0 +1,9 @@
1
+What:		ip_queue
2
+Date:		finally removed in kernel v3.5.0
3
+Contact:	Pablo Neira Ayuso <pablo@netfilter.org>
4
+Description:
5
+	ip_queue has been replaced by nfnetlink_queue which provides
6
+	more advanced queueing mechanism to user-space. The ip_queue
7
+	module was already announced to become obsolete years ago.
8
+
9
+Users:

+ 8 - 0
Documentation/ABI/removed/net_dma

@@ -0,0 +1,8 @@
1
+What:		tcp_dma_copybreak sysctl
2
+Date:		Removed in kernel v3.13
3
+Contact:	Dan Williams <dan.j.williams@intel.com>
4
+Description:
5
+	Formerly the lower limit, in bytes, of the size of socket reads
6
+	that will be offloaded to a DMA copy engine.  Removed due to
7
+	coherency issues of the cpu potentially touching the buffers
8
+	while dma is in flight.

+ 10 - 0
Documentation/ABI/removed/o2cb

@@ -0,0 +1,10 @@
1
+What:		/sys/o2cb symlink
2
+Date:		May 2011
3
+KernelVersion:	3.0
4
+Contact:	ocfs2-devel@oss.oracle.com
5
+Description:	This is a symlink: /sys/o2cb to /sys/fs/o2cb. The symlink is
6
+		removed when new versions of ocfs2-tools which know to look
7
+		in /sys/fs/o2cb are sufficiently prevalent. Don't code new
8
+		software to look here, it should try /sys/fs/o2cb instead.
9
+Users:		ocfs2-tools. It's sufficient to mail proposed changes to
10
+		ocfs2-devel@oss.oracle.com.

+ 15 - 0
Documentation/ABI/removed/raw1394

@@ -0,0 +1,15 @@
1
+What:		raw1394 (a.k.a. "Raw IEEE1394 I/O support" for FireWire)
2
+Date:		May 2010 (scheduled), finally removed in kernel v2.6.37
3
+Contact:	linux1394-devel@lists.sourceforge.net
4
+Description:
5
+	/dev/raw1394 was a character device file that allowed low-level
6
+	access to FireWire buses.  Its major drawbacks were its inability
7
+	to implement sensible device security policies, and its low level
8
+	of abstraction that required userspace clients to duplicate much
9
+	of the kernel's ieee1394 core functionality.
10
+	Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
11
+	firewire-core.
12
+
13
+Users:
14
+	libraw1394 (works with firewire-cdev too, transparent to library ABI
15
+	users)

+ 16 - 0
Documentation/ABI/removed/video1394

@@ -0,0 +1,16 @@
1
+What:		video1394 (a.k.a. "OHCI-1394 Video support" for FireWire)
2
+Date:		May 2010 (scheduled), finally removed in kernel v2.6.37
3
+Contact:	linux1394-devel@lists.sourceforge.net
4
+Description:
5
+	/dev/video1394/* were character device files, one for each FireWire
6
+	controller, which were used for isochronous I/O.  It was added as an
7
+	alternative to raw1394's isochronous I/O functionality which had
8
+	performance issues in its first generation.  Any video1394 user had
9
+	to use raw1394 + libraw1394 too because video1394 did not provide
10
+	asynchronous I/O for device discovery and configuration.
11
+	Replaced by /dev/fw*, i.e. the <linux/firewire-cdev.h> ABI of
12
+	firewire-core.
13
+
14
+Users:
15
+	libdc1394 (works with firewire-cdev too, transparent to library ABI
16
+	users)

+ 103 - 0
Documentation/ABI/stable/firewire-cdev

@@ -0,0 +1,103 @@
1
+What:		/dev/fw[0-9]+
2
+Date:		May 2007
3
+KernelVersion:	2.6.22
4
+Contact:	linux1394-devel@lists.sourceforge.net
5
+Description:
6
+		The character device files /dev/fw* are the interface between
7
+		firewire-core and IEEE 1394 device drivers implemented in
8
+		userspace.  The ioctl(2)- and read(2)-based ABI is defined and
9
+		documented in <linux/firewire-cdev.h>.
10
+
11
+		This ABI offers most of the features which firewire-core also
12
+		exposes to kernelspace IEEE 1394 drivers.
13
+
14
+		Each /dev/fw* is associated with one IEEE 1394 node, which can
15
+		be remote or local nodes.  Operations on a /dev/fw* file have
16
+		different scope:
17
+		  - The 1394 node which is associated with the file:
18
+			  - Asynchronous request transmission
19
+			  - Get the Configuration ROM
20
+			  - Query node ID
21
+			  - Query maximum speed of the path between this node
22
+			    and local node
23
+		  - The 1394 bus (i.e. "card") to which the node is attached to:
24
+			  - Isochronous stream transmission and reception
25
+			  - Asynchronous stream transmission and reception
26
+			  - Asynchronous broadcast request transmission
27
+			  - PHY packet transmission and reception
28
+			  - Allocate, reallocate, deallocate isochronous
29
+			    resources (channels, bandwidth) at the bus's IRM
30
+			  - Query node IDs of local node, root node, IRM, bus
31
+			    manager
32
+			  - Query cycle time
33
+			  - Bus reset initiation, bus reset event reception
34
+		  - All 1394 buses:
35
+			  - Allocation of IEEE 1212 address ranges on the local
36
+			    link layers, reception of inbound requests to such
37
+			    an address range, asynchronous response transmission
38
+			    to inbound requests
39
+			  - Addition of descriptors or directories to the local
40
+			    nodes' Configuration ROM
41
+
42
+		Due to the different scope of operations and in order to let
43
+		userland implement different access permission models, some
44
+		operations are restricted to /dev/fw* files that are associated
45
+		with a local node:
46
+			  - Addition of descriptors or directories to the local
47
+			    nodes' Configuration ROM
48
+			  - PHY packet transmission and reception
49
+
50
+		A /dev/fw* file remains associated with one particular node
51
+		during its entire life time.  Bus topology changes, and hence
52
+		node ID changes, are tracked by firewire-core.  ABI users do not
53
+		need to be aware of topology.
54
+
55
+		The following file operations are supported:
56
+