| /linux-3.3/Documentation/ |
| D | ManagementStyle | 5 on who you ask) management style for the linux kernel. It's meant to
11 to do with reality. It started as a lark, but that doesn't mean that it
14 Btw, when talking about "kernel manager", it's all about the technical
21 People", and NOT read it. Burn it, it's a great symbolic gesture.
24 making it painfully obvious to the questioner that we don't have a clue
34 manager must be to make it. That's very deep and obvious, but it's not
55 It helps to realize that the key difference between a big decision and a
70 It turns out that since nobody would be stupid enough to ever really let
71 a kernel manager have huge fiscal responsibility _anyway_, it's usually
78 you made a year ago wasn't a big decision after all, since it could be
[all …]
|
| D | HOWTO | 4 This is the be-all, end-all document on this topic. It contains
6 to work with the Linux kernel development community. It tries to not
22 and hints on how to work with the community. It will also try to
23 explain some of the reasons why the community works like it does.
35 The kernel is written using GNU C and the GNU toolchain. While it
36 adheres to the ISO C89 standard, it uses a number of extensions that are
40 divisions and floating point are not allowed. It can sometimes be
42 and the extensions that it uses, and unfortunately there is no
47 existing development community. It is a diverse group of people, with
75 new features are added to the kernel, it is recommended that new
[all …]
|
| D | dma-buf-sharing.txt | 9 buffer sharing API, how to use it for exporting and using shared buffers.
29 in memory, mapped into its own address space, so it can access the same area
40 1. Exporter announces that it wishes to export a buffer
42 passes it around to potential buffer-users based on use case
46 6. when buffer-user is done using this buffer completely, it 'disconnects'
52 The buffer exporter announces its wish to export a buffer. In this, it
62 pointer to the same. It also associates an anonymous file with this buffer,
63 so it can be exported. On failure to allocate the dma_buf object, it returns
69 anonymous file associated with the buffer. It can then share the fd with other
81 it.
[all …]
|
| D | IPMI.txt | 10 It provides for dynamic discovery of sensors in the system and the
12 values change or go outside certain boundaries. It also has a
23 subject and I can't cover it all here!
29 things to have it work right depending on your hardware. Most of
37 Kernel code (like the watchdog) can still use it. If you need access
42 properly provides the SMBIOS info for IPMI, the driver will detect it
47 support this, but it is unknown if it will work on every board. For
49 figuring to see if it will work on your system if the SMBIOS/APCI
50 information is wrong or not present. It is fairly safe to have both
67 watchdog timer start as soon as it initializes. It also have a lot
[all …]
|
| /linux-3.3/Documentation/filesystems/ |
| D | hpfs.txt | 9 is taken from it
16 Set owner/group/mode for files that do not have it specified in extended
25 - there is a list of text extensions (I thing it's better to not convert
27 change it in the source. Original readonly HPFS contained some strange
28 heuristic algorithm that I removed. I thing it's danger to let the
34 danger. I tried to write it so that it won't crash if check=normal on
36 used for debugging (for example it checks if file is allocated in
37 bitmaps when accessing it).
41 When to mark filesystem dirty so that OS/2 checks it.
63 access it under names 'a.', 'a..', 'a . . . ' etc.
[all …]
|
| D | porting | 51 informative error value to report). Call it foo_fill_super(). Now declare
80 it by internal locking (most of filesystems couldn't care less) - you
88 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
99 functions. If you don't need it, remove it.
105 free to drop it...
117 an existing filesystem, set it according to ->fs_flags:
121 FS_LITTER is gone - just remove it from fs_flags.
127 went in - and hadn't been documented ;-/). Just remove it from fs_flags
145 Briefly it allows for the definition of decode_fh and encode_fh operations
150 It is planned that this will be required for exporting once the code
[all …]
|
| /linux-3.3/drivers/staging/speakup/ |
| D | Kconfig | 7 This is the Speakup screen reader. Think of it as a
9 kernel, it can speak everything on the text console from
48 synthesizer. You can say y to build it into the kernel,
49 or m to build it as a module. See the configuration
56 synthesizer. You can say y to build it into the kernel,
57 or m to build it as a module. See the configuration
64 synthesizer. You can say y to build it into the kernel,
65 or m to build it as a module. See the configuration
72 You can say y to build it into the kernel, or m to
73 build it as a module. See the configuration help on the
[all …]
|
| /linux-3.3/drivers/staging/asus_oled/ |
| D | README | 11 It has been tested on Asus G1 and didn't cause any problems,
12 but I don't guarantee that it won't do anything wrong :)
14 It can (and probably does) have errors. It is usable
15 in my case, and I hope others will find it useful too!
27 It will build (hopefully) the module and install it in
30 To load it just use:
33 You can check if it has detected your OLED display by looking into dmesg output.
37 If it doesn't find your display, you can try removing usbhid module.
39 before usbhid, it will work even when usbhid is present.
41 If it still doesn't detect your hardware, check lsusb output.
[all …]
|
| /linux-3.3/Documentation/fb/ |
| D | matroxfb.txt | 11 * It provides a nice large console (128 cols + 48 lines with 1024x768)
22 How to use it?
82 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel
97 Driver contains SVGALib compatibility code. It is turned on by choosing textual
98 mode for console. You can do it at boot time by using videomode
101 Switching to another console and back fixes it. I hope that it is SVGALib's
115 it always probe for memory. Default is to use whole detected
120 configuration, you can override it by this (you cannot override
121 `off'). It is default.
122 noaccel - do not use acceleration engine. It does not work on Alphas.
[all …]
|
| /linux-3.3/Documentation/usb/ |
| D | persist.txt | 17 required to behave as though the device has been unplugged. It's a
20 device is still attached or perhaps it was removed and a different
26 though they had disconnected. This is always safe and it is the
32 system woke up, who cares? It'll still work the same when you type on
33 it.
49 it's as though you had unplugged all the USB devices. Yes, it's
61 the system can't be suspended at all. (All right, it _can_ be
62 suspended -- but it will crash as soon as it wakes up, which isn't
68 The kernel includes a feature called USB-persist. It tries to work
72 It works like this. If the kernel sees that a USB host controller is
[all …]
|
| /linux-3.3/net/netfilter/ |
| D | Kconfig | 44 Address Translation. It can also be used to enhance packet
47 To compile it as a module, choose M here. If unsure, say N.
112 the flow-stop time (once it has been destroyed) via Connection
140 If you want to compile it as a module, say M here and read
151 To compile it as a module, choose M here. If unsure, say N.
166 To compile it as a module, choose M here. If unsure, say N.
180 To compile it as a module, choose M here. If unsure, say N.
188 important VoIP protocols, it is widely used by voice hardware and
200 To compile it as a module, choose M here. If unsure, say N.
215 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-3.3/Documentation/power/ |
| D | pci.txt | 31 Usually, a device is put into a low-power state when it is underutilized or
32 completely inactive. However, when it is necessary to use the device once
33 again, it has to be put back into the "fully functional" state (full-power
50 to put the device that sent it into the full-power state. However, the PCI Bus
53 It is assumed that the platform firmware will perform this task and therefore,
54 even though a PCI device is set up to generate PMEs, it also may be necessary to
60 preparing the device to generate wakeup signals. In that case, however, it
71 introduced between the PCI 2.1 and PCI 2.2 Specifications. It defined a
76 but it is mandatory for PCI Express devices. If a device supports the PCI PM
77 Spec, it has an 8 byte power management capability field in its PCI
[all …]
|
| D | swsusp.txt | 14 * it may cause some problems, too. If you change kernel command line
15 * between suspend and resume, it may do something wrong. If you change
16 * your hardware while system is suspended... well, it was not good idea;
17 * but it will probably only crash.
19 * (*) suspend/resume support is needed to make it safe.
46 before suspend (it is limited to 500 MB by default).
56 Nowadays it is common in several laptops that they have a suspend button. It
59 ram and the machine can continue its work. It has two real benefits. First we
67 ``resume='' kernel option. If signature is found it loads and restores saved
68 state. If the option ``noresume'' is specified as a boot parameter, it skips
[all …]
|
| D | userland-swsusp.txt | 7 done it already.
22 reading, it is considered to be in the suspend mode. Otherwise it is
24 reading and writing. It is also impossible to have the device open more than
43 from it (0) (after resume the system finds itself finishing the
46 it out of the kernel
49 uploaded snapshot image; before calling it you should transfer
58 this number, but if it turns out to be impossible, the kernel will
79 partitions the offset is always 0, but it is different from zero for
91 be preceded by the SNAPSHOT_FREEZE call and it is also necessary
95 to disk, and then the system is suspended to RAM (this makes it possible
[all …]
|
| /linux-3.3/net/netfilter/ipvs/ |
| D | Kconfig | 23 If you want to compile it in kernel, say Y. To compile it as a
59 performance on it. You can adapt the table size yourself, according
60 to your virtual server application. It is good to set the table size
65 should be not far less than 200x200, it is good to set the table
120 If you want to compile it in kernel, say Y. To compile it as a
133 If you want to compile it in kernel, say Y. To compile it as a
143 If you want to compile it in kernel, say Y. To compile it as a
153 If you want to compile it in kernel, say Y. To compile it as a
160 destination IP load balancing. It is usually used in cache cluster.
167 If you want to compile it in kernel, say Y. To compile it as a
[all …]
|
| /linux-3.3/Documentation/vm/ |
| D | transhuge.txt | 12 Currently it only works for anonymous memory mappings but in the
13 future it can expand over the pagecache layer starting with tmpfs.
16 factors. The first factor is almost completely irrelevant and it's not
17 of significant interest because it'll also have the downside of
53 - it doesn't require memory reservation and in turn it uses hugepages
56 is not specific to transparent hugepage support and it's a generic
61 regions but it'd be ideal to move it to tmpfs and the pagecache
67 entities). It doesn't require reservation to prevent hugepage
68 allocation failures to be noticeable from userland. It allows paging
70 hugepages. It requires no modifications for applications to take
[all …]
|
| /linux-3.3/Documentation/filesystems/configfs/ |
| D | configfs.txt | 20 is discovered) and it is registered with sysfs. Its attributes then
22 readdir(3)/read(2). It may allow some attributes to be modified via
28 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
41 it by doing
47 subsystems. Once a client subsystem is loaded, it will appear as a
64 When an item needs to be destroyed, remove it with rmdir(2). An
65 item cannot be destroyed if any other item has a link to it (via
71 access remote block devices. Call it FakeNBD. FakeNBD uses configfs
74 the driver about it. Here's where configfs comes in.
76 When the FakeNBD driver is loaded, it registers itself with configfs.
[all …]
|
| /linux-3.3/Documentation/security/ |
| D | keys-request-key.txt | 47 does not need to link the key to a keyring to prevent it from being immediately
49 it's up to the caller to destroy the key.
80 a suitable key there. If there is, it returns the key. If there isn't,
84 (3) request_key() sees that A doesn't have the desired key yet, so it creates
102 Kerberos TGT key). It just requests the appropriate key, and the keyring
105 This will permit it to then search the keyrings of process A with the
106 UID, GID, groups and security info of process A as if it was process A,
109 (8) The program then does what it must to get the data with which to
110 instantiate key U, using key W as a reference (perhaps it contacts a
113 (9) Upon instantiating key U, auth key V is automatically revoked so that it
[all …]
|
| /linux-3.3/kernel/ |
| D | posix-cpu-timers.c | 115 if (timer->it.cpu.incr.sched == 0) in bump_cpu_timer()
121 if (now.sched < timer->it.cpu.expires.sched) in bump_cpu_timer()
123 incr = timer->it.cpu.incr.sched; in bump_cpu_timer()
124 delta = now.sched + incr - timer->it.cpu.expires.sched; in bump_cpu_timer()
131 timer->it.cpu.expires.sched += incr; in bump_cpu_timer()
138 if (now.cpu < timer->it.cpu.expires.cpu) in bump_cpu_timer()
140 incr = timer->it.cpu.incr.cpu; in bump_cpu_timer()
141 delta = now.cpu + incr - timer->it.cpu.expires.cpu; in bump_cpu_timer()
148 timer->it.cpu.expires.cpu += incr; in bump_cpu_timer()
175 * exported, but it is much more than 1s/HZ. in posix_cpu_clock_getres()
[all …]
|
| /linux-3.3/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 25 capability was also introduced with PCI 3.0. It supports more interrupts
43 it is possible that the interrupt may arrive before all the data has
75 and it may depend on some other options also being set. For example,
81 Most of the hard work is done for the driver in the PCI layer. It simply
105 If this function returns 0, it has succeeded in allocating at least as many
106 interrupts as the driver requested (it may have allocated more in order
109 the new interrupts assigned to it. The other interrupts assigned to
112 If this function returns a negative number, it indicates an error and
114 this device. If this function returns a positive number, it is
123 again. Note that it is not guaranteed to succeed, even when the
[all …]
|
| /linux-3.3/net/bridge/netfilter/ |
| D | Kconfig | 27 To compile it as a module, choose M here. If unsure, say N.
36 To compile it as a module, choose M here. If unsure, say N.
45 To compile it as a module, choose M here. If unsure, say N.
54 To compile it as a module, choose M here. If unsure, say N.
63 To compile it as a module, choose M here. If unsure, say N.
71 To compile it as a module, choose M here. If unsure, say N.
79 To compile it as a module, choose M here. If unsure, say N.
88 To compile it as a module, choose M here. If unsure, say N.
97 If you want to compile it as a module, say M here and read
108 To compile it as a module, choose M here. If unsure, say N.
[all …]
|
| /linux-3.3/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 115 13.13 When you run UML, it immediately segfaults
139 Welcome to User Mode Linux. It's going to be fun.
163 hardware, it talks to a `real' Linux kernel (called the `host kernel'
197 6. You can use it as a sandbox for testing new apps.
203 9. It's extremely fun.
237 3. Make a directory and unpack the kernel into it.
285 you want to change something, go ahead, it probably won't hurt
376 4. boot the kernel on it
432 It runs on 2.2.15 or later, and all 2.4 kernels.
435 Booting UML is straightforward. Simply run 'linux': it will try to
[all …]
|
| /linux-3.3/include/net/ |
| D | wimax.h | 9 * This program is free software; you can redistribute it and/or
10 * modify it under the terms of the GNU General Public License version
13 * This program is distributed in the hope that it will be useful,
34 * implement the backend support for it. However, device-specific
38 * Currently the messaging pipes are the only means of control as it
47 * private structure, initialize and register it. For details, see
57 * are the expected clients of it. They offer a higher level API that
106 * Each command/signal gets assigned it's own attribute policy. This
113 * here"? for each one. It can be done manually, but it's just easier
115 * it makes it easier to later expand each command/signal signature
[all …]
|
| /linux-3.3/ |
| D | COPYING | 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.
23 of this license document, but changing it is not allowed.
28 freedom to share and change it. By contrast, the GNU General Public
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
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
47 distribute copies of the software, or if you modify it.
69 program proprietary. To prevent this, we have made it clear that any
[all …]
|
| /linux-3.3/Documentation/scsi/ |
| D | qlogicfas.txt | 16 Nor does it support the PCI-Basic, which is supported by the
28 the Linux PCMCIA driver, you will have to adjust it or otherwise stop
29 it from configuring the card.
31 I am working with the PCMCIA group to make it more flexible, but that
37 configuration. As shipped, it provides a balance between speed and
42 It may be a good idea to enable RESET_AT_START, especially if the
45 command or something. It comes up faster if this is set to zero, and
46 if you have reliable hardware and connections it may be more useful to
51 Make sure it works properly under DOS. You should also do an initial FDISK
61 large executable or archive). It should be at least 5 megabytes, but
[all …]
|