| /linux-2.4.37.9/Documentation/arm/nwfpe/ |
| D | README | 4 The majority of the code was written by me, Scott Bambrough It is
6 where required. It was written quickly, with a goal of implementing a
17 Another choice I made was in the file structure. I have attempted to
30 SoftFloat to the ARM was done by Phil Blundell, based on an earlier
57 SoftFloat was written by John R. Hauser. This work was made possible in
59 1947 Center Street, Berkeley, California 94704. Funding was partially
61 original version of this code was written as part of a project to build
|
| /linux-2.4.37.9/fs/reiserfs/ |
| D | README | 40 fair, ask. (Last I spoke with him Richard was contemplating how best
84 Hans Reiser was the project initiator, primary architect, source of all
88 Vladimir Saveljev was one of the programmers, and he worked long hours
91 was quite remarkable. I don't think that money can ever motivate someone
99 substantial portion of the total code. He realized that there was a
106 tried to put me in a position where I was forced into giving control
109 really force takeovers of sole proprietorships.) This was something
111 why we should do what we do, or why innovation was possible in
112 general, but he was sure that he ought to be controlling it. Every
113 innovation had to be forced past him while he was with us. He added
[all …]
|
| /linux-2.4.37.9/Documentation/ |
| D | locks.txt | 14 The old flock(2) emulation in the kernel was swapped for proper BSD
29 Because sendmail was unable to use the old flock() emulation, many sendmail
31 for example. This gave rise to some other subtle problems if sendmail was
46 race and deadlock conditions that the current solution was the only
56 Mandatory locking, as described in 'Documentation/mandatory.txt' was prior
57 to this release a general configuration option that was valid for all
59 of which was the ability to freeze an NFS server by asking it to read a
|
| D | dnotify.txt | 15 DN_ACCESS A file in the directory was accessed (read)
16 DN_MODIFY A file in the directory was modified (write,truncate)
17 DN_CREATE A file was created in the directory
18 DN_DELETE A file was unlinked from directory
19 DN_RENAME A file in the directory was renamed
|
| D | using-newer-gcc.txt | 12 When Linux 2.4.0 was released in early 2001, GCC 2.95.2 was mainstream and
13 GCC 2.91.66 was still widely used. The GCC development model was evolving
21 build process. GCC 3.4 was a real pain to introduce as it required a lot of
23 work was less complicated thanks to the cleanup efforts invested in GCC 3.4.
61 - 3.4 : was recently introduced, received less testing, though seems
147 above, or /usr/local/bin if none was specified :
|
| D | watchdog-api.txt | 99 printf("The timeout was set to %d seconds\n", timeout);
101 This example might actually print "The timeout was set to 60 seconds"
108 printf("The timeout was is %d seconds\n", timeout);
132 The machine was last rebooted by the watchdog because the thermal limit was
141 External monitoring relay/source 1 was triggered. Controllers intended for
147 External monitoring relay/source 2 was triggered
155 The last reboot was caused by the watchdog card
165 The watchdog saw a keepalive ping since it was last queried.
|
| /linux-2.4.37.9/arch/m68k/ifpsp060/ |
| D | CHANGES | 33 1) "movep" emulation where data was being read from memory
34 was reading the intermediate bytes. Emulation now only
37 2) "flogn", "flog2", and "flog10" of "1" was setting the
42 mode was pre-decrement or post-increment and the address register
43 was A0 or A1, the address register was not being updated as a result
|
| /linux-2.4.37.9/Documentation/networking/ |
| D | lapb-module.txt | 136 LAPB_OK LAPB getparms was successful.
148 LAPB_OK LAPB getparms was successful.
150 LAPB_INVALUE One of the values was out of its allowable range.
224 LAPB_OK The LAPB link was terminated normally.
225 LAPB_NOTCONNECTED The remote system was not connected.
226 LAPB_TIMEDOUT No response was received in N2 tries from the remote
237 LAPB_OK The LAPB link was terminated normally by the remote
240 LAPB_NOTCONNECTED The remote system was not connected.
241 LAPB_TIMEDOUT No response was received in N2 tries from the remote
254 file include/linux/netdevice.h) if and only if the frame was dropped
|
| D | skfp.txt | 125 The functionality of the LED's on the FDDI network adapters was
132 With versions of SMT prior to v2.82 a ring up was indicated if the
133 yellow LED was off while the green LED(s) showed the connection
134 status of the adapter. During a ring down the green LED was off and
135 the yellow LED was on.
190 - Synchronization on SMP machines was buggy
|
| D | eql.txt | 12 which was only created to patch cleanly in the very latest kernel
242 up of the driver was tuned to handle slaves with wildly different
246 All testing I have done was with two 28.8 V.FC modems, one connecting
251 One version of the scheduler was able to push 5.3 K/s through the
265 o icee from LinuxNET patched 1.1.86 without any rejects and was able
363 Once a link was established, I timed a binary ftp transfer of
470 it over twin SL/IP lines, just over null modems, but I was
|
| /linux-2.4.37.9/drivers/char/ |
| D | README.epca | 241 much better if this code was placed in pc_init
273 1. A problem affecting hard flow control was found
278 incorrect. The solution was to change a line
285 2. In previous betas the cud device was set to CLOCAL
286 on driver boot up. Likewise the ttyD device was
297 0x1000) was used to reference our fbaud table a
328 ASYNC_NORMAL_ACTIVE. This code was redundant
333 was a CALLOUT device. CALLOUT devices never
334 block on CD. (This was a serious bug that
387 supported cards. (Code was also added to
[all …]
|
| /linux-2.4.37.9/fs/affs/ |
| D | Changes | 157 This was fixed before, but somehow got lost.
167 inode if the fs was not an OFS. This bug only shows
168 up if a file was enlarged via truncate() and there
169 was not enough space.
183 - Fixed bug in balloc(): Superblock was not set dirty after
184 the bitmap was changed, so the bitmap wasn't sync'd.
187 zone number was zero, the loop didn't terminate,
245 cache. If a file was extended by means of
298 was calculated and in the one following. This
|
| /linux-2.4.37.9/drivers/message/i2o/ |
| D | README.ioctl | 53 EFAULT Invalid user space pointer was passed
79 EFAULT Invalid user space pointer was passed
108 EFAULT Invalid user space pointer was passed
143 EFAULT Invalid user space pointer was passed
150 A return value of 0 does not mean that the value was actually
180 EFAULT Invalid user space pointer was passed
187 A return value of 0 does not mean that the value was actually
227 EFAULT Invalid user space pointer was passed
269 EFAULT Invalid user space pointer was passed
306 EFAULT Invalid user space pointer was passed
[all …]
|
| /linux-2.4.37.9/drivers/scsi/ |
| D | README.dpti | 23 * The original linux driver was ported to Linux by Karen White while at
24 * Dell Computer. It was ported from Bob Pasteur's (of DPT) original
31 * The driver was originally ported to linux version 2.0.34
34 * This was the first full GPL version since the last version used
|
| D | README.FlashPoint | 82 discover that the FlashPoint was not supported and would not be for quite
85 After this problem was identified, BusLogic contacted its major OEM
89 many purchasers of new systems, it was only a partial solution to the
93 ended up with a FlashPoint LT, believing it was supported, and were unable
100 it was best that these issues be addressed directly. I sent an email
138 I was a beta test site for the BT-948/958, and versions 1.2.1 and 1.3.1 of
140 Additional cosmetic support for the Ultra SCSI MultiMaster cards was added
145 are crucial to overall system stability. It was especially convenient
|
| /linux-2.4.37.9/Documentation/mips/pci/ |
| D | pci.README | 6 code in arch/mips/kernel. The code was ported from PowerPC and
9 each bridge. However, at the time this README was written, the
10 mips port was tested only on boards with a single pci bus and
|
| /linux-2.4.37.9/Documentation/usb/ |
| D | error-codes.txt | 67 -ENOENT URB was canceled by usb_unlink_urb
95 -EOVERFLOW The amount of data returned by the endpoint was
107 -ENODEV device was removed
|
| /linux-2.4.37.9/drivers/char/ftape/ |
| D | RELEASE-NOTES | 11 - fdc_probe() was calling DUMPREGS with a result length of "1" which
12 was just fine. Undo previous change.
16 - patches/2.x.x/floppy.c.diff was somewhat broken, releasing i/o
18 - fdc_probe() was calling DUMPREGS with a result length of "1" instead
66 segment without a good sector was reached ("wait for empty segment
92 complicated stuff has been moved to user space, so there was no
103 ftape-3.03b was released as a beta release only. Its main new feature
104 was support of the DITTO-2GB drive. This was made possible by reverse
122 * EOD (End Of Data) handling was still broken: the expected behavior
129 * Detection of QIC-40 cartridges in select_tape_format() was broken
[all …]
|
| /linux-2.4.37.9/fs/befs/ |
| D | ChangeLog | 7 * Fixed module makefile problem. It was not compiling all the correct
47 block being read. It was introduced when adding byteswapping in
105 * Removed notion of btree handle from btree.c. It was unessisary, as the
139 * Anton Altaparmakov figured out (by asking Linus :) ) what was causing the
189 * Fixed a thinko that was corrupting file reads after the first block_run
250 Subtle, because the old version was only sometimes wrong.
281 I have no intention of supporting it, and it was very ugly.
328 Make sure inode we got was the one we asked for.
339 * Fixed the problem with statfs where it would always claim the disk was
369 Not that it was possible to write before. But now the kernel won't even try.
|
| /linux-2.4.37.9/Documentation/filesystems/ |
| D | hpfs.txt | 106 file has a pointer to codepage it's name is in. However OS/2 was created in
111 Czech OS/2, the file was completely inaccessible under any name. It seems that
115 Czech OS/2 another file in that directory, that file was inaccessible too. OS/2
119 funny thing was that, when rebooted, PmShell tried to reopen this directory
122 system although HPFS was designed to allow that.
210 0.91 Fixed bug that caused shooting to memory when write_inode was called on
217 0.95 Fixed a bug that i_hpfs_parent_dir was not updated when moving files
231 1.92 Corrected a bug when sync was called just before closing file
241 (this bug was not destructive)
250 Fixed a bug that it set badly one flag in large anode tree (it was not
[all …]
|
| /linux-2.4.37.9/arch/i386/math-emu/ |
| D | README | 26 which was my 80387 emulator for early versions of djgpp (gcc under
27 msdos); wm-emu387 was in turn based upon emu387 which was written by
67 upon Newton's classic method. Performance was improved by capitalizing
71 "optimal" polynomial approximations. My definition of "optimal" was
120 operation was performed.
200 there was no reason not to use it after I had edited it to be
239 each function was tested at about 400 points. Ideal worst-case results
304 the transcendental functions (in their principal range) was not as
314 columns shows that an accuracy of between 63.80 and 63.89 bits was
321 the worst accuracy which was found (in bits) and the approximate value
[all …]
|
| /linux-2.4.37.9/fs/umsdos/ |
| D | specs | 12 * no easy way to tell that a directory was modified
62 * was modified during an MSDOS session, at least
95 * It was proposed that the sticky bit be used to set
128 * by proper directory locking. This was ensuring that only
130 * in the source and destination directory. This was also
131 * ensuring the operation was "atomic".
133 * This has been changed because this was creating a
141 * deadlock problem one tester was experiencing.
|
| /linux-2.4.37.9/Documentation/isdn/ |
| D | README.sc | 164 Upon testing, the following problem was noted, the driver would load without
165 problems, but the board would not respond beyond that point. When a check was
166 done with 'cat /proc/interrupts' the interrupt count for sc was 0. In the event
276 It was noted that in Beta Release 1, the module would fail to load and result
277 in a segmentation fault when 'insmod'ed. This problem was created when one of
278 the isdn4linux parameters, (isdn_ctrl, data field) was filled in. In some
279 cases, this data field was NULL, and was left unchecked, so when it was
|
| /linux-2.4.37.9/Documentation/crypto/ |
| D | descore-readme.txt | 29 This package was designed with the following goals:
56 since i was interested in fast des filters rather than crypt(3)
89 it's 39%-106% slower. because he was interested in fast crypt(3) and
123 so despite the comments in this code, it was possible to get
141 it was too convoluted, the code had been written without taking
144 it was excessively slow, the author had attempted to clarify the code
147 movement (in particular, his use of L1, R1, L2, R2), and it was full of
153 the fact that this guy was computing 2 sboxes per table lookup rather
155 do the same - it was a trivial change from which i had been scared away
171 one thing i did not want to do was write an enormous mess
[all …]
|
| /linux-2.4.37.9/Documentation/arm/SA1100/ |
| D | Itsy | 10 The port was done on an Itsy version 1.5 machine with a daughtercard with
31 The serial connection we established was at:
|