| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | NOTES | 13 f4 had been converted to an extended value in the emulator.
15 This is a side effect of the stfe instruction. The double in f4 had to be
16 converted to extended, then stored. If an lfm/sfm combination had been used,
|
| /linux-4.4.14/Documentation/ABI/removed/ |
| D | video1394 | 7 alternative to raw1394's isochronous I/O functionality which had
8 performance issues in its first generation. Any video1394 user had
|
| /linux-4.4.14/Documentation/usb/ |
| D | persist.txt | 26 though they had disconnected. This is always safe and it is the
36 devices. The effect is exactly the same as if the device really had
37 been unplugged while the system was suspended. If you had a mounted
49 it's as though you had unplugged all the USB devices. Yes, it's
74 reset or otherwise had lost power) then it applies a persistence check
83 kernel treats the device as though it had merely been reset instead of
93 behaves as though the old device had been unplugged and a new device
|
| D | iuu_phoenix.txt | 14 I never had any problem with it, but I'm not a real
|
| D | power-management.txt | 55 kernel had been built with CONFIG_USB_SUSPEND enabled (which depended on
58 enabled. The CONFIG_USB_SUSPEND option had been eliminated.]
|
| D | WUSB-Design-overview.txt | 405 a xfer abort request to the HC, cancel all the URBs we had submitted
|
| D | usb-serial.txt | 74 that have had a flash upgrade to a newer version of the OS. See the
|
| D | gadget-testing.txt | 458 in the past I had to apply the patch mentioned here:
|
| /linux-4.4.14/Documentation/locking/ |
| D | lockstat.txt | 46 contentions - number of lock acquisitions that had to wait
47 wait time min - shortest (non-0) time we ever had to wait for a lock
48 max - longest time we ever had to wait for a lock
62 that had to wait on lock acquisition.
|
| D | rt-mutex-design.txt | 70 inherited priority, and A then can continue with the resource that C had.
425 Before this function is called, the task has already had rt_mutex_adjust_prio
623 would add itself back when it realizes that it had the ownership stolen
651 in the loop, since it had just failed to get the mutex. But the second time
660 or if the task is a pending owner and had its mutex stolen. If the "task"
679 If the owner is also blocked on a lock, and had its pi_list changed
692 3) we had a timeout and was TASK_INTERRUPTIBLE
696 and on signal and timeout, will exit the loop, or if we had the mutex stolen
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | directory-locking | 64 the order until we had acquired all locks).
93 would have a contended child and we had assumed that no object is its
101 to (2) the order hadn't changed since we had acquired filesystem lock.
114 new parent had been equal to or a descendent of source since the moment when
115 we had acquired filesystem lock and rename() would fail with -ELOOP in that
|
| D | porting | 125 FS_SINGLE is gone (actually, that had happened back when ->get_sb()
208 ->revalidate() is gone. If your filesystem had it - provide ->getattr()
209 and let it call whatever you had as ->revlidate() + (for symlinks that
210 had ->revalidate()) add calls in ->follow_link()/->readlink().
218 * we know that parent had been locked (e.g. we are looking at
224 had been relying on BKL and that's prone to screwups. Old tree had quite
316 if it's zero is not *and* *never* *had* *been* enough. Final unlink() and iput()
354 via rcu-walk path walk (basically, if the file can have had a path name in the
|
| D | locks.txt | 59 had a number of inherent dangers, not the least of which was the ability to
|
| D | dnotify.txt | 20 DN_ATTRIB A file in the directory had its attributes
|
| D | xfs.txt | 209 after an underlying RAID device has had it's geometry
|
| D | seq_file.txt | 22 middle of a line of output. The kernel has traditionally had a number of
|
| D | path-lookup.txt | 278 parent snapshot fails, the house comes down, because we had closed the d_seq
|
| D | relay.txt | 362 occur yet, i.e. until the consumer has had a chance to read the
|
| D | vfs.txt | 268 had.
|
| /linux-4.4.14/scripts/ |
| D | checksyscalls.sh | 190 /* sync_file_range had a stupid ABI. Allow sync_file_range2 instead */
|
| /linux-4.4.14/Documentation/block/ |
| D | biovecs.txt | 53 it had to walk two different bios at the same time, keeping both bi_idx and
61 * Before, any code that might need to use the biovec after the bio had been
63 it somewhere else if there was an error) had to save the entire bvec array
83 bcache) had some ugly workarounds for this.
|
| D | stat.txt | 74 had I/O requests queued.
|
| D | data-integrity.txt | 58 calculating this checksum had a significant impact on system
|
| D | biodoc.txt | 851 Christoph Hellwig had some code that uses bios for page-io (rather than
|
| /linux-4.4.14/arch/cris/arch-v10/lib/ |
| D | csumcpfruser.S | 45 ;; Signal in *errptr that we had a failing access.
|
| /linux-4.4.14/arch/nios2/ |
| D | Kconfig.debug | 13 task has ever had available in the sysrq-T and sysrq-P debug output.
|
| /linux-4.4.14/arch/cris/arch-v32/lib/ |
| D | csumcpfruser.S | 45 ;; Signal in *errptr that we had a failing access.
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Transition-notes | 74 from pd.c. That could happen only if pi_do_claimed() had been
86 0 when pd_next_buf() had acquired pd_lock. If it become 0 while
88 the thread that had reset it would be in the area simulateously.
107 check its value is in ps_set_intr() and if it had been non-zero at that
|
| /linux-4.4.14/net/ax25/ |
| D | TODO | 12 The ax25_rt_find_route synopsys is pervert but I somehow had to deal with
|
| /linux-4.4.14/net/mpls/ |
| D | Kconfig | 22 that have had MPLS stack entries pushed onto them and thus
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mv64xxx.txt | 15 had broken offload support. Linux
|
| D | i2c-pxa-pci-ce4100.txt | 22 non-zero if you had 2 or more devices mapped off
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-bus-mdio | 27 device has had any "fixup" workaround running on it, encoded as
|
| D | sysfs-kernel-slab | 82 The alloc_slab file is shows how many times a new slab had to
210 been freed in a full slab so that it had to added to its node's
253 been freed to a now-empty slab so that it had to be removed from
|
| D | sysfs-driver-toshiba_acpi | 25 Note that the kernel 3.15 only had support for the first
|
| D | sysfs-block-bcache | 6 unregistered. If a backing device had dirty data in the cache,
|
| /linux-4.4.14/Documentation/ |
| D | bad_memory.txt | 38 some others. All had 0x1869xxxx in common, so I chose a pattern of
|
| D | stable_api_nonsense.txt | 51 Assuming that we had a stable kernel source interface for the kernel, a
118 which have had to maintain their older USB interfaces over time. This
125 relatively little pain. If Linux had to ensure that it will preserve a
127 the older, broken one would have had to be maintained over time, leading
|
| D | robust-futexes.txt | 59 approach had been pending for years, but they are still not completely
80 So something had to be done.
156 userspace had to do.
|
| D | workqueue.txt | 37 In the original wq implementation, a multi threaded (MT) wq had one
38 worker thread per CPU and a single threaded (ST) wq had one worker
49 while a ST wq one for the whole system. Work items had to compete for
58 higher level of concurrency, like async or fscache, had to implement
|
| D | DMA-ISA-LPC.txt | 60 Note: x86_64 had a broken DMA API when it came to ISA but has since
|
| D | unshare.txt | 92 allocated inactive task) unshare had to make minor reorganizational
228 etc, had roughly two components. The first component allocated
|
| D | stable_kernel_rules.txt | 69 (for example because it had to be backported) this must be very clearly
|
| D | applying-patches.txt | 113 Whenever patch applies a patch that it had to modify a bit to make it fit
143 message similar to that, then it means that patch had to adjust the location
175 two lines that had been split.
|
| D | ManagementStyle | 40 manage had better know the details better than you, so if they come to
77 work you had people work on for the last year. Suddenly the decision
|
| D | HOWTO | 494 opinion have had positive experiences.
589 don't give up, it's possible. Many have done it before, and each had to
598 to be based on text he had written, and to Randy Dunlap and Gerrit
|
| D | email-clients.txt | 223 Pine has had some whitespace truncation issues in the past, but these
|
| D | intel_txt.txt | 106 instruction had put them in and place them into a wait-for-SIPI
|
| D | SubmittingPatches | 531 If a person has had the opportunity to comment on a patch, but has not
605 formatting can be had with "git format-patch". The tools cannot create
|
| D | vfio.txt | 22 and compute accelerators. Prior to VFIO, these drivers had to either
|
| D | atomic_ops.txt | 257 the given new value. It returns the old value that the atomic variable v had
|
| D | kmemcheck.txt | 79 before kmemcheck has had a chance to handle the fault. If ftrace then
|
| D | memory-barriers.txt | 2627 it will still appear as if the full memory access had taken place as far as the
2644 their own loads and stores as if they had happened in program order.
|
| D | pinctrl.txt | 104 standard too (all these pads had names, too):
|
| D | devices.txt | 111 Older kernels had /dev/ramdisk (1, 1) here.
2594 It had to be moved due to an unfortunate conflict.
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | overview.txt | 8 had some limitations:-
12 Linux had different wm8731 drivers for 4 different SoC platforms.
|
| /linux-4.4.14/arch/frv/kernel/ |
| D | break.S | 82 # catch the return from a TLB-miss handler that had single-step disabled
273 # do the bit we had to skip
381 # do the bit we had to skip
|
| /linux-4.4.14/Documentation/RCU/ |
| D | trace.txt | 51 Displays counts of the reasons rcu_pending() decided that RCU had
249 else had completed an expedited grace period that satisfies the
403 o "rpq" is the number of times that the CPU had passed through
406 o "cbr" is the number of times that this CPU had RCU callbacks
407 that had passed through a grace period, and were thus ready
413 o "gpc" is the number of times that an old grace period had
416 o "gps" is the number of times that a new grace period had started,
420 callback-offload kthread had to be deferred in order to avoid
507 had already been initiated for the current grace period.
511 period that never had blocked. If it is already running, it
|
| D | stallwarn.txt | 126 is the number that had executed since boot at the time that this CPU
249 leading the realization that the CPU had failed.
|
| D | rcu_dereference.txt | 128 compiler knows that the pointer is NULL, you had better
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi-generic.txt | 73 Here is a list of linux kernels in the 2.4 series that had new version
83 For reference here is a list of linux kernels in the 2.2 series that had
|
| D | dpti.txt | 62 * Add code that checks if a device that had been taken offline is
|
| D | FlashPoint.txt | 92 operating system and then later decided to run Linux, or those who had
98 for the FlashPoint. Rumors of varying accuracy had been circulating
|
| D | ChangeLog.megaraid | 89 Root Cause: in uioc_t structure, one of member had misaligned and it
156 problem. I had to increase the loop counter to 0xFFFFFF. (6 F's)
211 problem had been a new warning showing up in sparse output on alpha
|
| D | ChangeLog.ncr53c8xx | 281 was read from the SFBR i/o register after the previous message had
323 queuing for a device that had this feature enabled.
418 Use SDID instead as actual target number. Just have had to
|
| D | in2000.txt | 80 1.25 had a nasty bug that bit people with swap partitions
|
| D | ChangeLog.sym53c8xx | 45 This point had been discussed at the list and the solution
342 (Btw, only problems with Toshiba 3401B had been reported).
530 - Some rewrite of the device detection code. This code had been
|
| D | sym53c8xx_2.txt | 174 modes. The SCSI SCRIPTS had been entirely rewritten using LOAD/STORE instead
212 All I can say is that I never have had problem with tagged queuing using
|
| D | ChangeLog.lpfc | 123 provided new log message number - had two 0326 entries.
629 replaces some of the attributes we had local to the driver).
660 from hbadisc.c, sli.c, and fcp.c since these modules had no
|
| D | scsi_mid_low_api.txt | 306 The Scsi_Host structure has had reference counting infrastructure added.
322 The Scsi_device structure has had reference counting infrastructure added.
|
| D | st.txt | 249 -b option) may have had good throughput but this is not true any more with
|
| D | ChangeLog.1992-1997 | 25 functions the request->dev field had into the device proper,
|
| D | ncr53c8xx.txt | 201 modes. The SCSI SCRIPTS had been entirely rewritten using LOAD/STORE instead
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-sched.txt | 36 are running on a CPU. A '*' denotes the CPU that had the event, and
|
| D | perf-trace.txt | 82 Show only events that had a duration greater than N.M ms.
|
| D | intel-pt.txt | 26 or "branches" events had been recorded. Presently 3 tools support this:
|
| /linux-4.4.14/arch/m32r/lib/ |
| D | checksum.S | 74 bgtz r1, 1f ; Jump if we had at least two bytes.
192 bgtz r1, 1f ; Jump if we had at least two bytes.
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | adm1021 | 95 2003) microarchitecture had real MAX1617, ADM1021, or compatible chips
97 era (with 400 MHz FSB) had chips with only one temperature sensor.
|
| D | abituguru-datasheet | 308 resulted in a _permanent_ reprogramming of the voltages, luckily I had the
|
| /linux-4.4.14/Documentation/arm/SA1100/ |
| D | serial_UART | 1 The SA1100 serial port had its major/minor numbers officially assigned:
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | cpqarray.txt | 36 necessary to specify the IRQ). For example, if you had two SMART-2/E
|
| D | paride.txt | 212 For example, if you had two no-name CD-ROM drives both using the
|
| /linux-4.4.14/arch/sh/lib/ |
| D | checksum.S | 78 bt/s 1f ! Jump if we had at least two bytes.
233 cmp/pz r6 ! Jump if we had at least two bytes.
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | Channel-Mapping-API.txt | 18 The problem, so far, was that we had no standard channel map
19 explicitly, and applications had no way to know which channel
|
| D | README.maya44 | 14 …ifficult to get detailed programming information, so I (Rainer Zimmermann) had to find out some ca…
|
| D | Audiophile-Usb.txt | 441 I had no success in testing this for now, if you have any success with this kind
|
| D | ALSA-Configuration.txt | 45 Prior to version 0.9.0rc4 options had a 'snd_' prefix. This was removed.
|
| /linux-4.4.14/Documentation/timers/ |
| D | hrtimers.txt | 108 settimeofday and NTP, all the timers (!) had to be dequeued, the
109 time-changing code had to fix them up one by one, and all of them had to
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.ir | 58 device, which had the effect that XFree86 recognised some of the keys
|
| D | README.pvrusb2 | 115 implementation had to be completely different.
191 the driver, but they had to go somewhere.
|
| D | v4l2-framework.txt | 26 This meant that all drivers had to do the setup of device instances and
683 In some cases you want to tell the core that a function you had specified in
|
| /linux-4.4.14/Documentation/crypto/ |
| D | descore-readme.txt | 69 improvements i had suggested to him, this package's
138 man pages either didn't exist or dumped core. i had heard of kerberos,
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
155 do the same - it was a trivial change from which i had been scared away
|
| /linux-4.4.14/Documentation/networking/ |
| D | netif-msg.txt | 14 From the beginning of Linux, each network device driver has had a local
|
| D | cxacru.txt | 8 so it had no effect on the device configuration. Fixing it could have stopped
|
| D | tlan.txt | 36 support such things) will work. I haven't had any solid evidence
|
| D | altera_tse.txt | 257 octets, and had either a bad CRC with an integral number of octets (CRC Error)
262 in length and had either a bad CRC with an integral number of octets (CRC
|
| D | 3c509.txt | 126 These are "mostly harmless" message indicating that the driver had too much
|
| D | dl2k.txt | 26 The driver support Linux kernel 2.4.7 later. We had tested it
|
| D | rxrpc.txt | 306 (4) If there is more data to be had on a call (it hasn't copied the last byte
821 Other errors may be returned if the call had been aborted (-ECONNABORTED)
822 or had timed out (-ETIME).
|
| D | netdev-FAQ.txt | 151 Generally speaking, the longer it has had a chance to "soak" in mainline,
|
| D | spider_net.txt | 127 In particular, it will clear the descriptor on which the hardware had
|
| D | filter.txt | 27 you had another filter that is still running: the kernel takes care of
607 The old format had two registers A and X, and a hidden frame pointer. The
966 They had to be carried over from classic to have strong performance of
|
| D | vortex.txt | 324 we've noticed for a while but haven't had the time to track down.
|
| D | phy.txt | 260 PHY may not have been reset or had fixups run yet.
|
| D | arcnet-hardware.txt | 374 tell me. I had to figure mine out without the manual, and it WASN'T FUN!
2256 When I got my two cards, one of them had this switch set to "enhanced". That
2258 card had this switch set to "compatible" and it behaved absolutely normally. I
2960 *I* have had success using RG59B/U with *NO* terminators!
|
| D | arcnet.txt | 295 which should use the same protocol as WfWg does. I had no luck
|
| D | bonding.txt | 1935 does not support or had some error in processing both the MII register
2787 then restore the MAC addresses that the slaves had before they were
|
| /linux-4.4.14/arch/x86/lib/ |
| D | checksum_32.S | 73 jae 1f # Jump if we had at least two bytes.
297 jae 1f # Jump if we had at least two bytes.
|
| /linux-4.4.14/Documentation/power/ |
| D | suspend-and-interrupts.txt | 18 block interrupts from them anyway. Also, in the past we had problems with
20 not prepared for interrupts triggering after their devices had been suspended.
|
| D | userland-swsusp.txt | 94 suspend image is first created, as though the system had been suspended
|
| D | runtime_pm.txt | 612 power, even if they had been suspended before the system suspend began. There
630 If the device had been suspended before the system suspend began and it's
655 be more efficient to leave the devices that had been suspended before the system
|
| D | devices.txt | 320 children of a device had been suspended if new children could be
371 generated by some other device after its own device had been set to low
|
| D | swsusp.txt | 137 * assume we had special "polling" ide driver that only uses memory
|
| /linux-4.4.14/fs/ceph/ |
| D | caps.c | 476 unsigned had = __ceph_caps_issued(ci, NULL); in __check_cap_issue() local
483 (had & (CEPH_CAP_FILE_CACHE|CEPH_CAP_FILE_LAZYIO)) == 0) { in __check_cap_issue()
493 (had & CEPH_CAP_FILE_SHARED) == 0) { in __check_cap_issue()
2578 void ceph_put_cap_refs(struct ceph_inode_info *ci, int had) in ceph_put_cap_refs() argument
2584 if (had & CEPH_CAP_PIN) in ceph_put_cap_refs()
2586 if (had & CEPH_CAP_FILE_RD) in ceph_put_cap_refs()
2589 if (had & CEPH_CAP_FILE_CACHE) in ceph_put_cap_refs()
2592 if (had & CEPH_CAP_FILE_BUFFER) { in ceph_put_cap_refs()
2600 if (had & CEPH_CAP_FILE_WR) in ceph_put_cap_refs()
2628 dout("put_cap_refs %p had %s%s%s\n", inode, ceph_cap_string(had), in ceph_put_cap_refs()
|
| D | super.h | 887 extern void ceph_put_cap_refs(struct ceph_inode_info *ci, int had);
|
| /linux-4.4.14/arch/x86/um/ |
| D | checksum_32.S | 61 jae 1f # Jump if we had at least two bytes.
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | README.ymfsb | 71 sounds from SPDIF-out of your card (if it had).
|
| D | Introduction | 323 when I had an IRQ conflict.
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | rockchip-io-domain.txt | 22 If there were some other software that had the smarts of making
|
| /linux-4.4.14/drivers/usb/core/ |
| D | Kconfig | 25 devices that lose power get reenumerated as if they had been
|
| /linux-4.4.14/Documentation/phy/ |
| D | samsung-usb2.txt | 13 the PHY powering up process had to be altered. This adaptation layer is
|
| /linux-4.4.14/drivers/gpu/drm/msm/ |
| D | NOTES | 76 names (I had to invent a few, since no sufficient hint was given in
|
| /linux-4.4.14/Documentation/nvmem/ |
| D | nvmem.txt | 14 drivers/misc, where they all had to duplicate pretty much the same code to
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | CHANGES | 46 4) Beta B.2 version had the following erratum:
|
| /linux-4.4.14/Documentation/ide/ |
| D | ide.txt | 107 jumpered as "single" or "master", *not* "slave". Many folks have had
154 setup; I've had one report of a system which was shipped with IRQ 15
|
| D | ChangeLog.ide-cd.1994-2004 | 167 * now set ionly for CD-R and CD-RW drives. I had
|
| D | ChangeLog.ide-tape.1995-2002 | 73 * Removed some old (non-active) code which had
|
| /linux-4.4.14/drivers/net/arcnet/ |
| D | Kconfig | 77 card you had, this is probably the one for you.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 3.Early-stage | 35 they had implemented; they were unwilling to accept alternatives. The
78 driver which duplicated an existing driver that the new author had been
|
| D | 6.Followthrough | 130 only turned up during the merge window and had to be addressed in a hurry.
140 may be a new round of comments from developers who had not been aware of
|
| D | 5.Posting | 221 - Cc: the named person received a copy of the patch and had the
234 which have had gratuitous white-space changes or line wrapping performed
|
| D | 7.AdvancedTopics | 69 rewritten as if it had been written on top of today's mainline, even though
|
| D | 4.Coding | 19 The kernel has long had a standard coding style, described in
273 paths had been exercised a few times.
|
| D | 2.Process | 6 course of one year, the kernel has since had to evolve a number of
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-nice-design.txt | 79 nice levels were not 'punchy enough', so lots of people had to resort to
|
| D | sched-design-CFS.txt | 90 way the previous scheduler had, and has no heuristics whatsoever. There is
|
| /linux-4.4.14/Documentation/vm/ |
| D | zswap.txt | 26 device when the compressed pool reaches its size limit. This requirement had
|
| D | userfaultfd.txt | 91 KVM kernel code had to be modified in order to add postcopy live
|
| D | numa_memory_policy.txt | 201 the selected node, as if the node had been specified by a Preferred
202 policy or had been selected by a local allocation. That is,
|
| D | hugetlbpage.txt | 198 specified in the mempolicy as if "interleave" had been specified.
|
| D | unevictable-lru.txt | 603 after shrink_active_list() had moved them to the inactive list, or pages mapped
|
| /linux-4.4.14/Documentation/ia64/ |
| D | serial.txt | 59 (This works only in 2.6.6 or later; prior to that you had
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | pxa_dma.txt | 84 - if Buffer1 and Buffer2 had all their addresses 8 bytes aligned
|
| /linux-4.4.14/fs/befs/ |
| D | ChangeLog | 59 they work. I had forgotten all about them. (inode.c, symlink.c) [WD]
321 * Permanently removed code that had been provisionally ifdefed out of befs_fs.h
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-class-tpm | 114 key if possible. If the TPM has had ownership established and
|
| D | sysfs-driver-ib_srp | 186 Description: Number of times the initiator had to wait before sending a
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | convert_drivers_to_kernel_api.txt | 5 Before the watchdog framework came into the kernel, every driver had to
|
| /linux-4.4.14/Documentation/mtd/ |
| D | nand_ecc.txt | 562 to 0.075 sec. Actually I had to decide to start measuring over 10
691 introduced by this is about a factor 2 on my system when a repair had to
692 be done, and 1% or so if no repair had to be done.
|
| /linux-4.4.14/arch/m32r/ |
| D | Kconfig | 60 The Mappi-I board was the first platform, which had been used
|
| /linux-4.4.14/arch/x86/math-emu/ |
| D | README | 200 there was no reason not to use it after I had edited it to be
293 have a value of pi which had about 150 bits precision. The FPU
|
| /linux-4.4.14/drivers/mtd/nand/ |
| D | Kconfig | 10 The original Linux implementation had byte 0 and 1 swapped.
186 using NAND. Early versions of the chips have had problems with
|
| /linux-4.4.14/Documentation/serial/ |
| D | moxa-smartio | 402 If major number 30 and 35 had been occupied, you may have to select
431 make sure you had run the "msmknod" utility.
|
| /linux-4.4.14/arch/cris/arch-v10/ |
| D | README.mm | 146 a fault before we have had time to jump into the real kernel segment (0xc0). This
|
| /linux-4.4.14/Documentation/input/ |
| D | joystick-api.txt | 300 The v0.8.0.2 driver also had an interface for 'digital joysticks', (now
|
| D | input-programming.txt | 199 struct for each absolute axis your device has. If our button device had also
|
| /linux-4.4.14/fs/reiserfs/ |
| D | README | 113 innovation had to be forced past him while he was with us. He added
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | xilinx.txt | 128 // If this device had extra parameters, then they would
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | blkio-controller.txt | 257 This is the amount of time the cgroup had to wait since it became busy
273 time it had a pending request and will not include the current delta.
|
| D | cpusets.txt | 619 allowed CPU placement is changed immediately. If such a task had been
633 tasks are attached to that cpuset, any pages that task had
657 violate cpuset placement, over starving a task that has had all
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | ide-cd | 240 had one report of a system which was shipped with IRQ 15 disabled
300 Some early Slackware releases had these defined incorrectly. If
|
| D | cdrom-standard.tex | 69 different \cdrom\ interfaces were developed. Some of them had their
77 scheme, either a separate driver had to be written, or an existing
78 driver had to be enhanced. History has delivered us \cdrom\ support for
89 features of the software interface had been added to accommodate the
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 620 Otherwise, if all pages had reads dispatched, then 0 will be returned, the
857 change - at which point the netfs has to throw away all the state it had for an
868 cache has had a chance to insert a barrier in the operations queue. After
|
| /linux-4.4.14/drivers/input/serio/ |
| D | Kconfig | 150 to keep using that driver until the new HIL drivers have had
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | rpc-cache.txt | 178 Note: If a cache has no active readers on the channel, and has had not
|
| /linux-4.4.14/drivers/macintosh/ |
| D | Kconfig | 132 devices are not fully supported in the bay as I never had one to
|
| /linux-4.4.14/Documentation/x86/ |
| D | exception-tables.txt | 14 in type (read or write). To do this, verify_read had to look up the
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | Cards | 179 "Flyvideo II" had been the name for the 848 cards, nowadays (in Germany)
193 Model 50680 got re-used, some model no. had different contents over time.
|
| /linux-4.4.14/Documentation/frv/ |
| D | mmu-layout.txt | 118 calling kunmap_atomic() if it had previously called kmap_atomic().
|
| /linux-4.4.14/Documentation/laptops/ |
| D | laptop-mode.txt | 85 anymore to write dirty blocks, because those blocks had already been written
560 # (A couple of early 2.6 laptop mode patches had these.)
|
| D | thinkpad-acpi.txt | 1456 0.18 had an earlier version that did strange things
|
| /linux-4.4.14/arch/arc/ |
| D | Kconfig | 371 Double Precision Floating Point unit had dedictaed regs which
|
| /linux-4.4.14/arch/xtensa/ |
| D | Kconfig | 199 before jumping to _startup in head.S and had an advantage that
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | eeh-pci-error-recovery.txt | 326 the sysadmin had the foresight to run /bin, /sbin, /etc, /var
|
| D | cxlflash.txt | 254 success, all "tokens" which had been provided to the user from the
|
| D | hvcs.txt | 284 the vty-server and vty connection before the target vty has had a chance to
|
| /linux-4.4.14/sound/oss/ |
| D | CHANGELOG | 345 had noticed it earlier.
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig.cpu | 321 Old PentiumPro multiprocessor systems had errata that could cause
|
| /linux-4.4.14/Documentation/i2c/ |
| D | writing-clients | 378 These ones were removed from i2c-core because they had no users, but could
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace.txt | 809 and one CPU buffer had a lot of events recently, thus
810 a shorter time frame, were another CPU may have only had
977 Here we see that that we had a latency of 16 microseconds (which is
982 recording the function that had that latency.
984 Note the above example had function-trace not set. If we set
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 204 (we had been leaving a file's mode read-only until the inode were reloaded).
666 wake up the demultiplex thread after it had exited. Do not log
843 at rmmod time). This had broken as a sideeffect of the recent global
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.gigaset | 35 We had also reports from users of Gigaset M105 who could use the drivers
|
| D | INTERFACE | 20 had a unique version number. The last version, distributed separately
|
| /linux-4.4.14/Documentation/arm64/ |
| D | acpi_object_usage.txt | 86 if it had actually occurred. However, this table should not be
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | hdio.txt | 117 are the "bios" values -- presumably the values the drive had
|
| /linux-4.4.14/drivers/ata/ |
| D | Kconfig | 886 the ixp4xx expansion bus. This driver had been written for
|
| /linux-4.4.14/arch/powerpc/ |
| D | Kconfig | 530 which had been compiled using binutils later than 2.17.50.0.3 with
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | booting-without-of.txt | 127 order to avoid the degeneration that had become the ppc32 kernel entry
989 under /chosen called interrupt-controller which had a phandle value
|
| /linux-4.4.14/Documentation/m68k/ |
| D | kernel-options.txt | 411 [I had to break this line...]
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 906 at a time so you nearly had to spend as long pruning the file down as you would
1740 You might now be thinking that the line above didn't work, something extra had
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | spkguide.txt | 833 onto the command line, just as though you had typed it in. Press the
1028 Again, these are part of the help system. For instance, if you had pressed
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 3169 thread's stack. I had been seeing the idle thread segfault for no
3171 of catching the culprit in the act, I had turned off all protections
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 552 task has ever had available in the sysrq-T and sysrq-P debug output.
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 716 * the list or only had one command to issue, NEXTSCB[1] is
|
| /linux-4.4.14/init/ |
| D | Kconfig | 780 as if rcu_expedite_gp() had been invoked early in boot.
|