| /linux-4.4.14/arch/arm/boot/dts/ |
| D | imx53-tx53.dtsi | 255 /* MX53_PAD_NANDF_CS2__GPIO6_15 0x1f4 maybe used by EDT-FT5x06 */
256 /* MX53_PAD_EIM_A16__GPIO2_22 0x1f4 maybe used by EDT-FT5x06 */
259 /* MX53_PAD_EIM_A17__GPIO2_21 0x1f4 maybe used by EDT-FT5x06 */
271 /* MX53_PAD_EIM_D22__GPIO3_22 0x1f4 maybe used by EETI touchpanel driver */
272 /* MX53_PAD_EIM_D23__GPIO3_23 0x1f4 maybe used by EETI touchpanel driver */
|
| D | kirkwood-b3.dts | 103 * Not yet identified what it is, maybe the eeprom
|
| /linux-4.4.14/Documentation/ |
| D | io_ordering.txt | 35 CPU A: (void)readl(safe_register); /* maybe a config register? */
42 CPU B: (void)readl(safe_register); /* maybe a config register? */
|
| D | xz.txt | 74 size for in-kernel use (maybe more is OK for initramfs). The presets
|
| D | svga.txt | 91 all consistent video modes supported by your BIOS will appear (plus maybe some
159 really want to have the adapter autodetected (maybe in case the `scan' feature
|
| D | rtc.txt | 134 example, maybe the low-power battery-backed RTC is a discrete I2C chip, but
|
| D | memory-hotplug.txt | 443 - allowing memory hot-add to ZONE_MOVABLE. maybe we need some switch like
|
| D | initrd.txt | 354 to build the right environment (maybe using the root= device passed on
|
| D | vfio.txt | 505 future IOMMU technologies will reduce some, but maybe not all, of
|
| D | dma-buf-sharing.txt | 142 accessing at the same time (for reading, maybe), or any other kind of sharing
|
| D | CodingStyle | 371 and it gets confused. You know you're brilliant, but maybe you'd like
|
| D | SubmittingPatches | 715 space (easily fit in 80 columns, maybe with some indentation). (git
|
| D | pinctrl.txt | 902 wake up and maybe even gpio_request/gpio_free as part of this cycle. This
|
| D | memory-barriers.txt | 2792 the kernel must flush the overlapping bits of cache on each CPU (and maybe
|
| D | devices.txt | 2885 maybe ParPort) versions may be driven via ide-scsi or
|
| D | kernel-parameters.txt | 3276 Test RCU priority boosting? 0=no, 1=maybe, 2=yes.
|
| /linux-4.4.14/drivers/parport/ |
| D | TODO-parport | 14 with (maybe just log) whatever the printer wants to tell the world.
|
| /linux-4.4.14/drivers/block/zram/ |
| D | Kconfig | 14 disks and maybe many more.
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | sunrpc.txt | 14 maybe a few other things as well.
|
| /linux-4.4.14/arch/tile/gxio/ |
| D | mpipe.c | 284 int maybe = in gxio_mpipe_rules_begin() local
287 if (maybe != 255) in gxio_mpipe_rules_begin()
288 stack = maybe; in gxio_mpipe_rules_begin()
|
| /linux-4.4.14/drivers/gpu/drm/omapdrm/ |
| D | TODO | 3 accessing the pages via a GART, so maybe we need some other threshold
|
| /linux-4.4.14/tools/testing/selftests/zram/ |
| D | README | 9 use as swap disks, various caches under /var and maybe many more :)
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | Locking | 26 d_revalidate: no no yes (ref-walk) maybe
28 d_hash no no no maybe
29 d_compare: yes no no maybe
36 d_manage: no no yes (ref-walk) maybe
143 statfs: maybe(read) (see below)
213 sync_page: maybe
349 fl_release_private: maybe maybe[1]
367 lm_compare_owner: yes[1] maybe no
|
| D | romfs.txt | 33 maybe even affs filesystem until you really know that you need it.
|
| D | logfs.txt | 126 corresponding to the 16 direct pointers in the inode. In ext2 (maybe
|
| D | hpfs.txt | 57 also won't be able to compile linux kernel (and maybe other things) on HPFS
|
| D | xfs-delayed-logging-design.txt | 14 than any other object (except maybe the superblock buffer) so keeping the
|
| D | vfs.txt | 752 If the VM wants to relocate a page (maybe off a memory card
|
| D | coda.txt | 1422 definitely is such a state change, but many others are maybe not).
|
| /linux-4.4.14/arch/cris/ |
| D | Kconfig.debug | 20 (gdb) target remote /dev/ttyS0 <- maybe you use another port
|
| /linux-4.4.14/net/decnet/ |
| D | TODO | 20 [maybe this should be done at socket level... the control data in the
|
| /linux-4.4.14/scripts/coccinelle/api/ |
| D | resource_size.cocci | 92 msg="WARNING: Suspicious code. resource_size is maybe missing with %s" % (x)
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | w83l785ts | 36 and cause read errors. Or maybe the W83L785TS-S chip is simply unreliable,
|
| D | asb100 | 28 controller will simply not work (or maybe it will for you... it doesn't for
|
| /linux-4.4.14/Documentation/i2c/ |
| D | ten-bit-addresses | 27 listed above could stay for a long time, maybe even forever if nobody
|
| D | fault-codes | 10 some cases, such as re-initializing (and maybe resetting). After such
58 than allowed. This usually indicates some device (maybe the
|
| /linux-4.4.14/Documentation/x86/ |
| D | early-microcode.txt | 12 the initrd image (maybe compressed). Kernel parses the combined initrd image
|
| /linux-4.4.14/arch/frv/kernel/ |
| D | switch_to.S | 176 # some CPUs have extra ACCx and ACCGx regs and maybe FSRx regs
419 # some CPUs have extra ACCx and ACCGx regs and maybe FSRx regs
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | gadget.xml.db | 20 API-usb-ep-align-maybe
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.cx88 | 47 (1) Try upgrading to the latest snapshot, maybe it has been added
|
| D | zr364xx.txt | 10 Possible chipsets are : ZR36430 (ZR36430BGC) and maybe ZR36431, ZR36440, ZR36442...
|
| D | README.pvrusb2 | 43 Linux APIs (V4L, sysfs, maybe DVB in the future).
|
| D | Zoran | 248 to generate PAL N, maybe it would work if you use the PAL M settings.
|
| D | v4l2-framework.txt | 1103 the ops argument itself maybe NULL.
|
| /linux-4.4.14/Documentation/ide/ |
| D | ChangeLog.ide-floppy.1996-2002 | 25 * IDEFLOPPY_CAPABILITIES_PAGE, but maybe it's just me.
|
| /linux-4.4.14/drivers/auxdisplay/ |
| D | Kconfig | 114 You can freeze the computer, or the LCD maybe can't draw as fast as you
|
| /linux-4.4.14/Documentation/s390/ |
| D | DASD | 34 provide support of partitions, maybe VTOC oriented or using a kind of
|
| /linux-4.4.14/Documentation/RCU/ |
| D | lockdep-splat.txt | 70 And maybe that lock really does protect this reference. If so, the fix
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | fw-memory.txt | 65 3 processors on chip, Java ones, VPU, SPU, APU, maybe these are the
|
| /linux-4.4.14/Documentation/fb/ |
| D | matroxfb.txt | 297 + maybe more...
311 them (maybe that chip overheats, but it has a very big cooler (G100 has
321 + maybe more...
|
| D | framebuffer.txt | 88 If you try to change that information, the driver maybe will round up some
95 it to the hardware (round it down to less bits, maybe throw away
|
| /linux-4.4.14/Documentation/sound/oss/ |
| D | SoundPro | 58 -and maybe-
|
| D | README.modules | 59 uart401.o # Used by sb, maybe other cards
|
| D | README.OSS | 431 (maybe ALSxxx chips too but they probably don't work).
1355 (limited by the OSS-design). Development has started and maybe
1412 to all low level drivers and be tested too, maybe with multiple
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-summary | 205 maybe coupling it with code to initialize pin configurations, so that
313 onto a card that's maybe just thirty square centimeters. On such systems,
390 (two pointers, maybe the same one in both cases) and half
479 bus number (maybe the same as the platform device ID) and three methods
|
| /linux-4.4.14/Documentation/scsi/ |
| D | libsas.txt | 81 address from the IDENTIFY frame or maybe generate a SAS
117 lldd_port -- I haven't found use for that -- maybe other
|
| D | in2000.txt | 57 in 'in2000_queuecommand()' and maybe 1 or 2 other places.
|
| D | osst.txt | 8 get them started using (and maybe debugging) it.
|
| D | ChangeLog.megaraid | 243 asserting that it must be held (maybe just for
256 maybe it's not advised to make such assertions,
|
| D | tmscsim.txt | 399 maybe the DC390 log messages to the report.
|
| /linux-4.4.14/Documentation/arm/ |
| D | Interrupts | 50 the various operations (maybe this'll change to a better name).
|
| /linux-4.4.14/Documentation/dvb/ |
| D | faq.txt | 118 all then maybe the PID is wrong. If there are error packets,
|
| D | README.dvb-usb | 35 Objective is to migrate all the usb-devices (dibusb, cinergyT2, maybe the
|
| /linux-4.4.14/Documentation/power/ |
| D | video.txt | 19 using vbetool later, or maybe nothing is necessary on particular
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | zram.txt | 10 use as swap disks, various caches under /var and maybe many more :)
|
| /linux-4.4.14/Documentation/usb/ |
| D | persist.txt | 159 maybe fail because they may morph after reset.
|
| D | ehci.txt | 169 so that it's only trying six (or maybe seven) USB transactions each
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | compress_offload.txt | 226 maybe dealt in user-library
|
| D | Audiophile-Usb.txt | 436 * (maybe) patching the alsa-lib/src/pcm/pcm_multi.c file (see the ice1712 page)
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | botching-up-ioctls.txt | 211 maybe only your testsuite needs this interface, and then debugfs with its
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | sched-deadline.txt | 465 - (c)group based bandwidth management, and maybe scheduling;
487 workloads (maybe mimicking real use-cases) and evaluate how the scheduler
|
| /linux-4.4.14/drivers/usb/gadget/ |
| D | Kconfig | 40 don't have this kind of hardware (except maybe inside Linux PDAs).
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 6.Followthrough | 196 kernel, nobody has absolute veto power over any code. Except maybe Linus.
|
| /linux-4.4.14/Documentation/input/ |
| D | joystick-parport.txt | 12 and maybe even more. Like when a lightning kills you it is not our problem.
|
| /linux-4.4.14/Documentation/vm/ |
| D | frontswap.txt | 193 or maybe swap-over-nbd/NFS)?
|
| /linux-4.4.14/Documentation/m68k/ |
| D | kernel-options.txt | 101 [Strange and maybe uninteresting stuff ON]
119 [Strange and maybe uninteresting stuff OFF]
|
| /linux-4.4.14/ |
| D | Makefile | 611 KBUILD_CFLAGS += -Os $(call cc-disable-warning,maybe-uninitialized,)
|
| D | MAINTAINERS | 85 Orphan: No current maintainer [but maybe you could take the
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | fpsp.S | 954 # maybe we can make these entry points ONLY the OVFL entry points of each routine.
13544 beq.w fabs_sd_may_ovfl # maybe; go check
13587 beq.w fabs_sd_may_ovfl # maybe; go check
14337 beq.w fsgldiv_may_unfl # maybe
14630 # occurred. If so, return default result and maybe EXOP. Else, insert #
14694 beq.w fadd_may_unfl # maybe; go find out
15083 # occurred. If so, return default result and maybe EXOP. Else, insert #
15147 beq.w fsub_may_unfl # maybe; go find out
|
| D | pfpsp.S | 953 # maybe we can make these entry points ONLY the OVFL entry points of each routine.
|
| /linux-4.4.14/Documentation/mtd/ |
| D | nand_ecc.txt | 441 Well, it was expected not to be easy so maybe instead move to a
|
| /linux-4.4.14/Documentation/networking/ |
| D | arcnet-hardware.txt | 281 IRQ 5 - FREE (LPT2 if you have it; sometimes COM3; maybe PLIP)
360 ON OFF Never happens (maybe when wrong ID)
1895 jumpers and maybe one of J18-J21 selects ROM. Also J6-J10 and
|
| /linux-4.4.14/drivers/watchdog/ |
| D | Kconfig | 1040 from Vision Systems and maybe others.
|
| /linux-4.4.14/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 1029 and maybe reduce the life of the backlight lamps by needlessly kicking
|
| /linux-4.4.14/Documentation/block/ |
| D | biodoc.txt | 399 passed around different types of subsystems or layers, maybe even
|
| /linux-4.4.14/drivers/video/fbdev/ |
| D | Kconfig | 1709 and maybe other boards.
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 4272 If you're not listed here and you think maybe you should be, please
|