| /Documentation/networking/ |
| D | depca.txt | 8 64K on on on on d0000 dbfff
9 off on on on c0000 cbfff
10 off off on on e0000 ebfff
12 32K on on off on d8000 dbfff
13 off on off on c8000 cbfff
14 off off off on e8000 ebfff
16 DBR ROM on on dc000 dffff
17 off on cc000 cffff
20 Note that the 2K mode is set by SW3/SW4 on/off or off/off. Address
25 0x300 on
[all …]
|
| D | 00-INDEX | 4 - information on the 3Com EtherLink Plus (3c505) driver.
6 - info on the 6pack protocol, an alternative to KISS for AX.25
8 - info on the D-Link DE-600/DE-620 parallel port pocket adapters
12 - info on General Instrument/NextLevel SURFboard1000 cable modem.
14 - info on using alias network devices
16 - tons of info on ARCnet, hubs, jumper settings for ARCnet cards, etc.
18 - info on the using the ARCnet driver itself.
20 - info on where to get ATM programs and support for Linux.
22 - info on using AX.25 and NET/ROM code for Linux
24 - info on the driver for Baycom style amateur radio modems
[all …]
|
| /Documentation/ |
| D | 00-INDEX | 5 Please try and keep the descriptions small enough to fit on one line.
8 Following translations are available on the WWW:
16 - info on kernel <-> userspace ABI and relative interface stability.
25 - An extended tutorial on how to work with the kernel development
38 - info on Linux Intelligent Platform Management Interface (IPMI) Driver.
40 - how to select which CPU(s) handle which interrupt events on SMP.
46 - directory with info on RCU (read-copy update).
48 - info on Secure Attention Keys.
62 - documentation on accounting and taskstats.
64 - info on ACPI-specific hooks in the kernel.
[all …]
|
| D | rt-mutex-design.txt | 64 process blocks on a lock owned by the current process. To make this easier
67 This time, when A blocks on the lock owned by C, C would inherit the priority
80 blocked on one of its locks. This is described in more detail
84 PI and spin locks that are used in the PI code, from now on
87 lock - In this document from now on, I will use the term lock when
90 CONFIG_PREEMPT is enabled) and on SMP prevents multiple CPUs from
95 waiter - A waiter is a struct that is stored on the stack of a blocked
97 a process being blocked on the mutex, it is fine to allocate
98 the waiter on the process's stack (local variable). This
100 the task is blocked on. It also has the plist node structures to
[all …]
|
| D | debugging-via-ohci1394.txt | 15 ask the OHCI-1394 controller to perform read and write requests on
26 space which can be a problem on IA64 machines where memory is located
27 mostly above that limit, but it is rarely a problem on more common
28 hardware such as hardware based on x86, x86-64 and PowerPC.
32 buffer on to debug early boot problems in areas like ACPI where the system
49 Because ohci1394 and firewire-ohci depend on the PCI enumeration to be
52 called, i.e. before the printk buffer appears on the console.
55 Remote debugging over FireWire early on boot) and pass the parameter
56 "ohci1394_dma=early" to the recompiled kernel on boot.
83 disable all physical DMA on each bus reset.
[all …]
|
| D | robust-futex-ABI.txt | 7 futexes, for kernel assist of cleanup of held locks on task exit.
9 The interesting data as to what futexes a thread is holding is kept on a
23 threads in the kernel. Options on the sys_futex(2) system call support
24 waiting on a particular futex, and waking up the next waiter on a
30 to do so, then improperly listed locks will not be cleaned up on exit,
32 waiting on the same locks.
41 consisting of three words. Each word is 32 bits on 32 bit arch's, or 64
42 bits on 64 bit arch's, and local byte order. Each thread should have
45 If a thread is running in 32 bit compatibility mode on a 64 native arch
49 compatibility mode, will attempt to process both lists on each task
[all …]
|
| D | svga.txt | 10 kernel decompression starts) and works only on 80X86 machines.
13 ** enter `scan' on the video mode prompt, pick the mode you want to use,
23 NORMAL_VGA - Standard 80x25 mode available on all display adapters.
25 EXTENDED_VGA - Standard 8-pixel font mode: 80x43 on EGA, 80x50 on VGA.
30 modes available on your adapter, you can specify the menu item you want
36 0x.... - Hexadecimal video mode ID (also displayed on the menu, see below
77 well (some of these might be missing or unusable on your machine as different
79 on the VGA BIOS).
81 The modes displayed on the menu are partially sorted: The list starts with
90 strange noises will be heard from inside the monitor and so on and then, really
[all …]
|
| /Documentation/isdn/ |
| D | README.act2000 | 18 on on on on 0x0200 (Factory default)
19 off on on on 0x0240
20 on off on on 0x0280
21 off off on on 0x02c0
22 on on off on 0x0300
23 off on off on 0x0340
24 on off off on 0x0380
25 on on on off 0xcfe0
26 off on on off 0xcfa0
27 on off on off 0xcf60
[all …]
|
| D | 00-INDEX | 2 - this file (info on ISDN implementation for Linux)
8 - general info on what you need and what to do for Linux ISDN.
16 - info on the ICN-ISDN-card and its driver.
18 - info on the HiSax driver which replaces the old teles.
20 - info on hfc-pci based cards.
22 - info on the PCBIT-D ISDN adapter and driver.
24 - info on running Sync PPP over ISDN.
28 - info on driver for AVM-B1 ISDN card.
30 - info on driver for IBM ACT-2000 card.
32 - info on driver for Eicon active cards.
[all …]
|
| D | README | 65 write: raw D-channel-messages (format: depends on driver).
66 read: raw D-channel-messages (format: depends on driver).
67 ioctl: depends on driver, i.e. for the ICN-driver, the base-address of
68 the ports and the shared memory on the card can be set and read
95 ATE1 Echo on (default).
126 AT&Lx Set list of phone numbers to listen on. x is a
147 Note on value in Reg 19:
157 AT&X1 BTX-mode on. (S13.1=1, S13.5=0 S14=0, S16=7, S18=7, S19=0)
158 AT&X2 T.70-mode on. (S13.1=1, S13.5=1, S14=0, S16=7, S18=7, S19=0)
175 0 0 Answer on ring number.
[all …]
|
| /Documentation/scsi/ |
| D | 00-INDEX | 4 - info on driver for 53c700 based adapters
6 - info on driver for adapters with BusLogic chips
26 - info on driver for BusLogic FlashPoint adapters
32 - info on driver for Mylex adapters
34 - info on WorkBiT NinjaSCSI-32/32Bi driver
38 - info on driver for Adaptec AHA152x based adapters
42 - info on driver for Adaptec controllers
44 - info on driver for Adaptec controllers, old generation
50 - info on driver for DPT SmartRAID and Adaptec I2O RAID based adapters
52 - info on driver for DTC 2x80 based adapters
[all …]
|
| D | in2000.txt | 46 The memory-mapped hardware on the card is now accessed via
50 forces an artificial 1023 track limit on drives. Also
62 can also use it to change a few run-time parameters on
76 grindstone on this one.
89 Big help from Bill Earnest and David Willmore on speed
97 now selectively disable sync on individual devices -
99 comments. Some of you disable the BIOS on the card, which
114 jury is still out on speed - I hope it's improved some.
155 on off D8000 - DBFF0
156 off on D0000 - D3FF0
[all …]
|
| D | scsi_fc_transport.txt | 34 port to appear on as multiple communication ports. Using the N_Port Id
37 separate port to other endpoints on the fabric, even though it shares one
39 unique view of the fabric based on fabric zoning and array lun-masking
43 obtain an N_Port_ID on each fabric it joins. Each fabric will have its
46 on each virtual fabric.
58 on the vport, resulting in a unique <H,C,T,L> namespace for the vport.
59 Thus, whether a FC port is based on a physical port or on a virtual port,
65 discussion will concentrate on NPIV.
96 and then the vport is created on the Physical Port:
113 /sys/class/fc_remote_ports/rport-17:0-0 rport on the physical port
[all …]
|
| /Documentation/filesystems/ |
| D | 00-INDEX | 2 - this file (info on some of the filesystems supported by linux).
6 - info on locking rules as they pertain to Linux VFS.
28 - info on the cram filesystem for small storage (ROMs etc).
30 - info on the RCU-based dcache locking model.
34 - info on the userspace interface to the OCFS2 DLM.
38 - docs on eCryptfs: stacked cryptographic filesystem for Linux.
46 - info on file management in the Linux kernel.
48 - info on the Filesystem in User SpacE including mount options.
50 - info on the Global File System 2.
52 - info on the Macintosh HFS Filesystem for Linux.
[all …]
|
| D | directory-locking | 1 Locking scheme used for directory operations is based on two
49 (1) if object removal or non-cross-directory rename holds lock on A and
50 attempts to acquire lock on B, A will remain the parent of B until we
51 acquire the lock on B. (Proof: only cross-directory rename can change
54 (2) if cross-directory rename holds the lock on filesystem, order will not
56 renames will be blocked on filesystem lock and we don't start changing
59 (3) any operation holds at most one lock on non-directory object and
63 Now consider the minimal deadlock. Each process is blocked on
66 not contended, since any process blocked on it is not holding any locks.
67 Thus all processes are blocked on ->i_mutex.
[all …]
|
| D | ubifs.txt | 27 5 Eraseblocks may become bad (only on NAND flashes) and software should
28 deal with this. Blocks on hard drives typically do not become bad,
35 UBIFS works on top of UBI. UBI is a separate software layer which may be
47 * JFFS2 works on top of MTD devices, UBIFS depends on UBI and works on
49 * JFFS2 does not have on-media index and has to build it while mounting,
51 information on the flash media and does not require full media scan,
54 which makes UBIFS much faster on writes.
56 Similarly to JFFS2, UBIFS supports on-the-flight compression which makes
61 journal and recovers from crashes, ensuring that the on-flash data
66 on the flash size, like in case of JFFS2. This is because UBIFS
[all …]
|
| D | tmpfs.txt | 5 created on your hard drive. If you unmount a tmpfs instance,
11 be adjusted on the fly via 'mount -o remount ...'
16 RAM, where you have to create an ordinary filesystem on top. Ramdisks
19 Since tmpfs lives completely in the page cache and on swap, all tmpfs
21 as shared or something like that. Further on you can check the actual
31 This mount does not depend on CONFIG_TMPFS. If CONFIG_TMPFS is not
41 Remember to create the directory that you intend to mount tmpfs on
50 e.g. on /tmp and /var/tmp and have a big swap partition. And now
65 is half of the number of your physical RAM pages, or (on a
70 can be changed on remount. The size parameter also accepts a suffix %
[all …]
|
| /Documentation/fb/ |
| D | 00-INDEX | 9 - info on the fbdev driver for ARK Logic chips.
11 - info on the ATI Rage128 frame buffer driver.
13 - info on the driver for Cirrus Logic chipsets.
23 - info on the generic EFI platform driver for Intel based Macs.
31 - info on the Matrox framebuffer driver for Alpha, Intel and PPC.
33 - info on the video mode database.
35 - info on the Matrox frame buffer driver.
37 - info on the PowerVR 2 frame buffer driver.
39 - info on the driver for the PXA25x LCD controller.
41 - info on the fbdev driver for S3 Trio/Virge chips.
[all …]
|
| D | s3fb.txt | 17 - probably not working on big endian
19 I tested s3fb on Trio64 (plain, V+ and V2/DX) and Virge (plain, VX, DX),
20 all on i386.
29 * 24 bpp truecolor mode (RGB 888) on (only on Virge VX)
30 * 32 bpp truecolor mode (RGB 888) on (not on Virge VX)
39 lower pixclocks (maximum usually between 50-60 MHz, depending on specific
43 support is broken on S3 Trio64 V2/DX.
50 Suspend/resume works on systems that initialize video card during resume and
62 * 24 bpp mode support on more cards
78 * text mode broken on S3 Trio64 V2/DX
|
| D | matroxfb.txt | 6 This is a driver for a graphic framebuffer for Matrox devices on
13 * You can run XF{68,86}_FBDev or XFree86 fbdev driver on top of /dev/fb0
33 unless you have primary display on non-Matrox VBE2.0 device (see
87 XFree servers have big troubles in multihead configurations (even on first
97 Driver contains SVGALib compatibility code. It is turned on by choosing textual
116 memory usable for on-screen display (i.e. max. 8 MB).
122 noaccel - do not use acceleration engine. It does not work on Alphas.
146 strange pattern on screen and so on. Devices not enabled by BIOS
170 nomtrr - disables write combining on frame buffer. This slows down driver but
173 mtrr - enables write combining on frame buffer. It speeds up video accesses
[all …]
|
| /Documentation/serial/ |
| D | 00-INDEX | 4 - info on Cyclades-Z firmware loading.
6 - info on Computone Intelliport II/Plus Multiport Serial Driver.
8 - info on Digi Intl. {PC,PCI,EISA}Xx and Xem series cards.
10 - info on using the Hayes ESP serial driver.
12 - file with info on installing/using Moxa multiport serial driver.
14 - notes on using the RISCom/8 multi-port serial driver.
16 - info on the Comtrol RocketPort multiport serial driver.
18 - info on hardware/driver for specialix IO8+ multiport serial card.
20 - info on using the Stallion multiport serial driver.
22 - info on the Specialix SX/SI multiport serial driver.
|
| /Documentation/video4linux/cx2341x/ |
| D | fw-osd-api.txt | 50 Bit 0 0=off, 1=on
61 0=off, 1=on
134 global alpha: 0=off, 1=on
145 global alpha: 0=off, 1=on
149 local alpha: 0=on, 1=off
169 flicker state: 0=off, 1=on
178 State: 0=off, 1=on
260 Same as Param[0] on API 0x52
262 Same as Param[1] on API 0x52
264 Same as Param[2] on API 0x52
[all …]
|
| /Documentation/s390/ |
| D | 00-INDEX | 14 - information on the DASD disk device driver.
16 - hints for debugging on s390 systems.
18 - information on s390 devices and the driver model.
20 - information on accessing the z/VM monitor stream from Linux.
22 - information on using the s390 debug feature.
24 - information on the driver for channel-attached tapes.
26 - information on the s390 SCSI dump tool.
|
| /Documentation/PCI/ |
| D | MSI-HOWTO.txt | 18 when this text talks about enabling or disabling MSI on a "device
20 not to all functions on a PCI device (unless the PCI device has only
30 to request service by sending an Inbound Memory Write on its PCI bus to
85 Due to increasing pressure on chipset and processor packages to
103 By default, the kernel will not enable MSI/MSI-X on all devices that
122 more than one vector. To enable MSI on a device function's MSI
131 enabled on its device function must call this API to enable MSI.
148 Note that a device driver should always call free_irq() on the MSI vector
149 that it has done request_irq() on before calling this API. Failure to do
156 mode on the MSI-capable device function between MSI mode and
[all …]
|
| /Documentation/hwmon/ |
| D | w83627ehf | 32 the temperature gets higher than high limit; it stays on until the temperature
98 different functions on the 627EHF and the 627DHG. Some registers also have
99 different power-on default values, but BIOS should already be loading
103 0x49: only on DHG, selects temperature source for AUX fan, CPU fan0
106 input selection to SmartFan I, not just SmartFan III. Testing on the EHF
110 0x5e: only on DHG, has bits to enable "current mode" temperature detection and
112 0x45b: only on EHF, bit 3, vin4 alarm (EHF supports 10 inputs, only 9 on DHG)
113 0x552: only on EHF, vin4
114 0x558: only on EHF, vin4 high limit
115 0x559: only on EHF, vin4 low limit
[all …]
|