| /linux-2.4.37.9/Documentation/isdn/ |
| D | INTERFACE.fax | 4 Description of the fax-subinterface between linklevel and hardwarelevel of
11 command ISDN_CMD_SETL3 (parm.fax). This pointer expires in case of hangup
18 In receive-mode the LL-driver takes care of the bit-order conversion
59 Defines the actual state of fax connection. Set by HL or LL
60 depending on progress and type of connection.
61 If the phase changes because of an AT command, the LL driver
62 changes this value. Otherwise the HL-driver takes care of it, but
64 (one of the constants ISDN_FAX_PHASE_[IDLE,A,B,C,D,E])
80 the end of connection for the +FHNG message.
84 ISDN_TTY_FAX_CFR output of +FCFR message.
[all …]
|
| /linux-2.4.37.9/arch/i386/math-emu/ |
| D | README | 9 | it under the terms of the GNU General Public License version 2 as |
13 | but WITHOUT ANY WARRANTY; without even the implied warranty of |
17 | You should have received a copy of the GNU General Public License |
26 which was my 80387 emulator for early versions of djgpp (gcc under
33 facets of the functioning of the FPU are not well covered in the
36 possible to be sure that all of the peculiarities of the 80486 have
38 in the detailed behaviour of the emulator and a real 80486.
40 wm-FPU-emu does not implement all of the behaviour of the 80486 FPU,
41 but is very close. See "Limitations" later in this file for a list of
56 ----------------------- Internals of wm-FPU-emu -----------------------
[all …]
|
| /linux-2.4.37.9/Documentation/powerpc/ |
| D | ppc_htab.txt | 12 The ppc_htab interface is a user level way of accessing the
23 Explanation of the 604 Performance Monitoring Fields:
24 MMCR0 - the current value of the MMCR0 register
26 PMC2 - the value of the performance counters and a
27 description of what events they are counting
29 Explanation of the PTE Hash Table fields:
32 Buckets - number of buckets in the table.
33 Address - the virtual kernel address of the hash table base.
34 Entries - the number of ptes that can be stored in the hash table.
36 Overflows - How many of the entries are in their secondary hash location.
[all …]
|
| /linux-2.4.37.9/Documentation/arm/ |
| D | Setup | 11 should not be referenced outside of arch/arm/kernel/setup.c:setup_arch().
13 There are a lot of parameters listed in there, and they are described
18 This parameter must be set to the page size of the machine, and
23 This is the total number of pages of memory in the system. If
25 of pages in the system.
44 major/minor number pair of device to mount as the root filesystem.
49 These two together describe the character size of the dummy console,
54 the equivalent character size of your fbcon display. This then allows
60 This describes the character position of cursor on VGA console, and
76 Number of ADFS/MFM disks. May be used differently by different
[all …]
|
| /linux-2.4.37.9/ |
| D | COPYING | 4 of the kernel, and does *not* fall under the heading of "derived work".
6 Foundation, but the instance of code that it refers to (the Linux
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
23 of this license document, but changing it is not allowed.
31 General Public License applies to most of the Free Software
37 When we speak of free software, we are referring to freedom, not
39 have the freedom to distribute copies of free software (and charge for
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.
[all …]
|
| /linux-2.4.37.9/drivers/net/e1000/ |
| D | LICENSE | 13 Everyone is permitted to copy and distribute verbatim copies of this license
22 to most of the Free Software Foundation's software and to any other program
27 When we speak of free software, we are referring to freedom, not price. Our
29 to distribute copies of free software (and charge for this service if you
31 can change the software or use pieces of it in new free programs; and that
37 copies of the software, or if you modify it.
39 For example, if you distribute copies of such a program, whether gratis or
56 wish to avoid the danger that redistributors of a free program will
68 terms of this General Public License. The "Program", below, refers to any
71 work containing the Program or a portion of it, either verbatim or with
[all …]
|
| /linux-2.4.37.9/drivers/sound/ |
| D | COPYING | 7 of this license document, but changing it is not allowed.
15 General Public License applies to most of the Free Software
21 When we speak of free software, we are referring to freedom, not
23 have the freedom to distribute copies of free software (and charge for
25 if you want it, that you can change the software or use pieces of it
31 distribute copies of the software, or if you modify it.
33 For example, if you distribute copies of such a program, whether
51 patents. We wish to avoid the danger that redistributors of a free
64 under the terms of this General Public License. The "Program", below,
67 that is to say, a work containing the Program or a portion of it,
[all …]
|
| /linux-2.4.37.9/fs/hfs/ |
| D | COPYING | 7 of this license document, but changing it is not allowed.
15 General Public License applies to most of the Free Software
21 When we speak of free software, we are referring to freedom, not
23 have the freedom to distribute copies of free software (and charge for
25 if you want it, that you can change the software or use pieces of it
31 distribute copies of the software, or if you modify it.
33 For example, if you distribute copies of such a program, whether
51 patents. We wish to avoid the danger that redistributors of a free
64 under the terms of this General Public License. The "Program", below,
67 that is to say, a work containing the Program or a portion of it,
[all …]
|
| /linux-2.4.37.9/drivers/net/e100/ |
| D | LICENSE | 13 Everyone is permitted to copy and distribute verbatim copies of this license
22 to most of the Free Software Foundation's software and to any other program
27 When we speak of free software, we are referring to freedom, not price. Our
29 to distribute copies of free software (and charge for this service if you
31 can change the software or use pieces of it in new free programs; and that
37 copies of the software, or if you modify it.
39 For example, if you distribute copies of such a program, whether gratis or
56 wish to avoid the danger that redistributors of a free program will
68 terms of this General Public License. The "Program", below, refers to any
71 work containing the Program or a portion of it, either verbatim or with
[all …]
|
| /linux-2.4.37.9/Documentation/sysctl/ |
| D | fs.txt | 12 miscellaneous and general things in the operation of the Linux
13 kernel. Since some of the files _can_ be used to screw up your
62 The file dquot-max shows the maximum number of cached disk
65 The file dquot-nr shows the number of allocated disk quota
66 entries and the number of free disk quota entries.
68 If the number of free cached disk quotas is very low and
69 you have some awesome number of simultaneous system users,
79 The value in file-max denotes the maximum number of file-
81 of error messages about running out of file handles, you might
84 The three values in file-nr denote the number of allocated
[all …]
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | packet_mmap.txt | 6 socket interface on 2.4 and 2.6 kernels. This type of sockets is used for
10 You can find the latest version of this document at
29 needs to wait for them, most of the time there is no need to issue a single
31 also has the benefit of minimizing packet copies.
33 It's fine to use PACKET_MMAP to improve the performance of the capture process,
35 is relative to the cpu speed), you should check if the device driver of your
36 network interface card supports some sort of interrupt load mitigation or
47 Said that, at time of this writing, official libpcap 0.8.1 is out and doesn't include
50 I'm aware of two implementations of PACKET_MMAP in libpcap:
55 The rest of this document is intended for people who want to understand
[all …]
|
| D | z8530drv.txt | 1 This is a subset of the documentation. To use this driver you MUST have the
12 A new version of the documentation, along with links to other important
32 1. Initialization of the driver
38 2. Setup of hardware, MODEM and KISS parameters with sccinit
42 driver. If you want to run xNOS instead of our fine kernel AX.25
50 (If you're going to compile the driver as a part of the kernel image,
59 You should include the insmod in one of the /etc/rc.d/rc.* files,
60 and don't forget to insert a call of sccinit after that. It
67 of your rc.*-files. This has to be done BEFORE you can
72 The file itself consists of two main sections.
[all …]
|
| /linux-2.4.37.9/Documentation/filesystems/ |
| D | ntfs.txt | 11 from a complete loss of data. Also, download the Linux-NTFS project
14 NTFS partition from Linux to fix some of the damage done by the Linux NTFS
28 For ftdisk support, limited success was reported with volume sets on top of
31 using the md driver will fail if any of your NTFS partitions have an odd
32 number of sectors.
43 to use the iocharset=utf8 which should be capable of
59 as hard links instead of being suppressed.
70 remount). Values of 1 to 4 are allowed, 1 being the
75 amount of free space. However, it can have an impact
76 on performance by affecting fragmentation of the MFT.
[all …]
|
| D | ext2.txt | 6 Theodore Ts'o and Stephen Tweedie, it was a major rewrite of the
20 check=none, nocheck (*) Don't do extra checking of bitmaps on mount
31 nogrpid, sysvgroups (*) New objects have the group ID of their creator.
45 the concepts of blocks, inodes and directories. It has space in the
56 a fixed size, of 1024, 2048 or 4096 bytes (8192 bytes on Alpha systems),
59 and also impose other limits on the size of files and the filesystem.
65 and minimise the amount of head seeking when reading a large amount
66 of consecutive data. Information about each block group is kept in a
68 Two blocks near the start of each group are reserved for the block usage
71 that the maximum size of a block group is 8 times the size of a block.
[all …]
|
| D | proc.txt | 13 Table of Contents
48 This documentation is part of a soon (or so we hope) to be released book on
61 We'd like to thank Alan Cox, Rik van Riel, and Alexey Kuznetsov and a lot of
66 and helped create a great piece of software... :)
72 The latest version of this document is available online at
82 We don't guarantee the correctness of this document, and if you come to us
83 complaining about how you screwed up your system because of incorrect
93 * Investigating the properties of the pseudo file system /proc and its
105 First, we'll take a look at the read-only parts of /proc. In Chapter 2, we
124 environ Values of environment variables
[all …]
|
| /linux-2.4.37.9/fs/cramfs/ |
| D | README | 23 null-padded to a multiple of 4 bytes.
25 The order of inode traversal is described as "width-first" (not to be
26 confused with breadth-first); i.e. like depth-first but listing all of
38 regular file of non-zero st_size.
44 padding to multiple of 4 bytes
46 The i'th <block_pointer> for a file stores the byte offset of the
47 *end* of the i'th <block> (i.e. one past the last byte, which is the
48 same as the start of the (i+1)'th <block> if there is one). The first
52 The order of <file_data>'s is a depth-first descent of the directory
57 <block>: The i'th <block> is the output of zlib's compress function
[all …]
|
| /linux-2.4.37.9/drivers/atm/ |
| D | fore200e_firmware_copyright | 2 These microcode data are placed under the terms of the GNU General Public License.
4 We would prefer you not to distribute modified versions of it and not to ask
9 are a trade secret of FORE Systems, Inc. or its subsidiaries or affiliates
15 behalf of the U.S. Government ("Government"), the following provisions apply
16 to you. If the software is supplied to the Department of Defense ("DoD"), it
18 of the DoD Supplement to the Federal Acquisition Regulations ("DFARS") (or any
21 users). If the Software is supplied to any unit or agency of the Government
23 the Government's rights in the Software are defined in paragraph 52.227-19 of
25 in the cases of NASA, in paragraph 18.52.227-86 of the NASA Supplement to the FAR
29 ForeThought are trademarks of FORE Systems, Inc. All other brands or product
[all …]
|
| /linux-2.4.37.9/Documentation/BK-usage/ |
| D | 00-INDEX | 1 bk-kernel-howto.txt: Description of kernel workflow under BitKeeper
3 bk-make-sum: Create summary of changesets in one repository and not
10 bksend: Create readable text output containing summary of changes, GNU
11 patch of the changes, and BK metadata of changes (as needed for proper
13 suitable for emailing BitKeeper changes. The recipient of this output
18 version of the compressed input.
20 csets-to-patches: Produces a delta of two BK repositories, in the form
21 of individual files, each containing a single cset as a GNU patch.
28 cset-to-linus: Produces a delta of two BK repositories, in the form of
|
| /linux-2.4.37.9/Documentation/ia64/ |
| D | efirtc.txt | 11 The purpose of this driver is to supply an API for kernel and user applications
16 driver. We describe those calls as well the design of the driver in the
22 at first, the time of day service. This is required in order to access, in a
24 to initialize the system view of the time during boot.
33 EFI uses a slightly different way of representing the time, noticeably
36 expose this new way of representing time. Instead we use something very
38 One of the reasons for doing it this way is to allow for EFI to still evolve
39 without necessarily impacting any of the user applications. The decoupling
42 The driver exposes two interfaces, one via the device file and a set of
45 As of today we don't offer a /proc/sys interface.
[all …]
|
| /linux-2.4.37.9/Documentation/cdrom/ |
| D | cdrom-standard.tex | 35 the widest variety of hardware devices. The reasons for this are
39 The large list of hardware devices available for the many platforms
42 The open design of the operating system, such that anybody can write a
45 There is plenty of source code around as examples of how to write a driver.
47 The openness of \linux, and the many different types of available
50 all these different devices has also allowed the behavior of each
52 This divergence of behavior has been very significant for \cdrom\
55 their drivers totally inconsistent, the writers of \linux\ \cdrom\
63 drivers should implement them. Currently (as of the \linux\ 2.1.$x$
69 different \cdrom\ interfaces were developed. Some of them had their
[all …]
|
| /linux-2.4.37.9/Documentation/vm/ |
| D | balance | 8 to incur cost overheads of page stealing and possible swap io for
13 In the absence of non sleepable allocation requests, it seems detrimental
15 is, only when needed (aka zone free memory is 0), instead of making it
19 mapped pages from the direct mapped pool, instead of falling back on
22 OTOH, if there is a lot of free dma pages, it is preferable to satisfy
24 of incurring the overhead of regular zone balancing.
27 _total_ number of free pages fell below 1/64 th of total memory. With the
28 right ratio of dma and regular memory, it is quite possible that balancing
30 been running production machines of varying memory sizes, and seems to be
31 doing fine even with the presence of this problem. In 2.3, due to
[all …]
|
| /linux-2.4.37.9/Documentation/ |
| D | ftape.txt | 8 2.08; the latter was the version of ftape delivered with the kernel
10 re-unification of ftape-2.x and zftape. zftape was developed in
14 as a feature or bug of zftape).
22 file located in the top level directory of the Linux kernel source
56 Unluckily, the ftape-HOWTO is out of date. This really needs to be
58 versions of ftape and useful links to related topics can be found at
70 The goal of all that incompatibilities was to give ftape an interface
75 The concept of a fixed block size for read/write transfers is
77 interface level. It developed out of a feature of zftape, a
80 reasons with previous releases of zftape.
[all …]
|
| /linux-2.4.37.9/Documentation/x86_64/ |
| D | mm.txt | 3 o per process virtual address space limit of 512 Gigabytes
4 o top of userspace stack located at address 0x0000007fffffffff
5 o start of the kernel mapping = 0x0000010000000000
7 o no need of any common code change
8 o 512GB of vmalloc/ioremap space
12 some extensions. Each level consits of a 4K page with 512 64bit
18 pagetables (pgd_offset() implicitly walks the 1st slot of the 4th
29 as the top of the userspace stack to allow the stack to grow as
34 kernel mapping is at the end of (negative) virtual address space to exploit
44 architectural dependent physical layout of the virtual to physical
[all …]
|
| /linux-2.4.37.9/Documentation/m68k/ |
| D | kernel-options.txt | 24 1) Overview of the Kernel's Option Processing
27 The kernel knows three kinds of options on its command line:
33 To which of these classes an argument belongs is determined as
37 argument contains an '=', it is of class 2, and the definition is put
42 the version mentioned at the start of this file. Later revisions may
45 In general, the value (the part after the '=') of an option is a
46 list of values separated by commas. The interpretation of these values
47 is up to the driver that "owns" the option. This association of
71 combination of two or three letters, followed by a decimal number.
94 partition number. Internally, the value of the number is just
[all …]
|
| /linux-2.4.37.9/Documentation/i386/ |
| D | zero-page.txt | 1 Summary of empty_zero_page layout (kernel point of view)
4 The contents of empty_zero_page are used to pass parameters from the
5 16-bit realmode code of the kernel to the 32-bit part. References/settings
21 Address of commandline is calculated:
22 0x90000 + contents of CL_OFFSET
33 0x1e8 char number of entries in E820MAP (below)
34 0x1e9 unsigned char number of entries in EDDBUF (below)
35 0x1f1 char size of setup.S, number of sectors
37 0x1f4 unsigned short size of compressed kernel-part in the
45 0x200 short jump to start of setup code aka "reserved" field.
[all …]
|