| /linux-4.1.27/drivers/media/usb/gspca/stv06xx/ |
| D | stv06xx_vv6410.c | 255 unsigned int fine, coarse; in vv6410_set_exposure() local
259 fine = val % VV6410_CIF_LINELENGTH; in vv6410_set_exposure()
263 coarse, fine); in vv6410_set_exposure()
265 err = stv06xx_write_sensor(sd, VV6410_FINEH, fine >> 8); in vv6410_set_exposure()
269 err = stv06xx_write_sensor(sd, VV6410_FINEL, fine & 0xff); in vv6410_set_exposure()
|
| /linux-4.1.27/Documentation/fb/ |
| D | aty128fb.txt | 41 XF68_FBDev should generally work fine, but it is non-accelerated. As of
42 this document, 8 and 32bpp works fine. There have been palette issues
|
| D | gxfb.txt | 35 XF68_FBDev should generally work fine, but it is non-accelerated.
|
| D | lxfb.txt | 35 XF68_FBDev should generally work fine, but it is non-accelerated.
|
| D | tgafb.txt | 57 mmap(). Running the standard XF86_TGA server from XFree86 3.3.x works fine for
|
| D | tridentfb.txt | 22 2. The ramdac speeds require some more fine tuning. It is possible to
|
| D | vesafb.txt | 83 XF68_FBDev should work just fine, but it is non-accelerated. Running
|
| D | matroxfb.txt | 82 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel
84 works fine.
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | boost.txt | 32 functionality at all, but a more fine-grained and dynamic control would
77 Though the per CPU existence hints at a more fine grained control, the
88 More fine grained boosting control
|
| D | cpufreq-stats.txt | 80 This will give a fine grained information about all the CPU frequency
117 provides fine grained cpufreq stats by trans_table. The reason for having a
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ieee802154/ |
| D | at86rf230.txt | 15 - xtal-trim: u8 value for fine tuning the internal capacitance
|
| /linux-4.1.27/drivers/powercap/ |
| D | Kconfig | 28 fine grained control. These domains include processor package, DRAM
|
| /linux-4.1.27/Documentation/block/ |
| D | biovecs.txt | 81 * Submitting partially completed bios is now perfectly fine - this comes up
86 fine to _most_ devices, but since accessing the raw bvec array was the
90 perfectly fine.
|
| D | biodoc.txt | 1034 idle for a while may not always make sense. The trick is to handle the fine
|
| /linux-4.1.27/drivers/staging/media/ |
| D | Kconfig | 8 so, they won't likely work fine with the existing applications.
|
| /linux-4.1.27/drivers/staging/slicoss/ |
| D | TODO | 30 - locking too fine grained, not designed just throw more locks
|
| /linux-4.1.27/drivers/net/can/softing/ |
| D | Kconfig | 13 The API of the card does not allow fine control per bus, but
|
| /linux-4.1.27/arch/microblaze/ |
| D | Kconfig.platform | 15 fine if both source and destination are aligned on the same
|
| /linux-4.1.27/fs/nfsd/ |
| D | Kconfig | 101 Say Y here if you want enable fine-grained security label attribute
106 If you do not wish to enable fine-grained security labels SELinux or
|
| /linux-4.1.27/Documentation/devicetree/bindings/spi/ |
| D | spi-rockchip.txt | 28 Rx data (may need to be fine tuned for high capacitance lines).
|
| /linux-4.1.27/Documentation/arm/SA1100/ |
| D | serial_UART | 11 > tty device layer handles this just fine, so you don't have to worry about
|
| /linux-4.1.27/arch/powerpc/platforms/ps3/ |
| D | Kconfig | 24 defaults should be fine for most users, but these options may make
40 This option is only for experts who may have the desire to fine
|
| /linux-4.1.27/fs/jffs2/ |
| D | TODO | 9 - fine-tune the allocation / GC thresholds
|
| /linux-4.1.27/net/openvswitch/ |
| D | Kconfig | 14 expected in a traditional hardware switch, it enables fine-grained
|
| /linux-4.1.27/Documentation/scsi/ |
| D | scsi_eh.txt | 18 [2-1] EH through fine-grained callbacks
169 LLDD can implement fine-grained EH callbacks and let SCSI
193 [2-1] EH through fine-grained callbacks
206 others are performed by invoking one of the following fine-grained
284 EH through fine-grained callbacks start from scsi_unjam_host().
|
| D | ChangeLog.sym53c8xx_2 | 144 as Paul Mackerras stated that MMIO works fine now on this arch.
|
| D | scsi-changer.txt | 69 works fine with small (11 slots) and a huge (4 MOs, 88 slots)
|
| D | in2000.txt | 20 It appears that the driver works fine with serial
|
| D | ChangeLog.megaraid | 280 Other than this, it looks fine to me too.
603 vii. Do not use "host_lock', driver has fine-grain locks now to protect all
|
| D | libsas.txt | 292 PHYE_OOB_DONE -- OOB went fine and oob_mode is valid
|
| D | ChangeLog.sym53c8xx | 341 to testing for a PHASE. SYMBIOS say this feature is working fine.
346 be fine.
|
| D | scsi_mid_low_api.txt | 753 slave_configure - driver fine tuning for given device after attach
1123 * slave_configure - driver fine tuning for given device just after it
|
| D | sym53c8xx_2.txt | 196 way for doing IO with PCI devices. Memory mapped I/O seems to work fine on
|
| D | ncr53c8xx.txt | 228 mapped I/O seems to work fine on most hardware configurations, but
|
| D | ChangeLog.lpfc | 810 it handles the empty list case just fine and the additional
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | README.cx88 | 56 "lspci -v" output is fine too).
|
| D | uvcvideo.txt | 87 The API doesn't currently provide a fine-grained access control facility. The
|
| /linux-4.1.27/Documentation/input/ |
| D | cs461x.txt | 12 Raw mode works fine with analog joystick front-end driver and cs461x
|
| D | xpad.txt | 46 is some limitation of jstest, since the input device setup should be fine. I
78 If you have an unknown xbox controller, it should work just fine with
|
| D | joystick.txt | 126 is met, then it's all fine, and you can play the games. :)
|
| /linux-4.1.27/Documentation/fmc/ |
| D | API.txt | 46 the time you read this it is already used by the spec-sw and fine-delay
|
| D | mezzanine.txt | 120 gateware=fmc/fine-delay.bin,fmc/simple-dio.bin
|
| D | identifiers.txt | 140 the fine-delay driver, and must live at a known address of 0x1800. By
|
| /linux-4.1.27/Documentation/devicetree/bindings/phy/ |
| D | apm-xgene-phy.txt | 17 - apm,tx-eye-tuning : Manual control to fine tune the capture of the serial
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ |
| D | stmmac.txt | 45 If not passed then the system clock will be used and this is fine on some
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | gl518sm | 59 alarms work fine, though.
|
| /linux-4.1.27/fs/reiserfs/ |
| D | Kconfig | 52 Almost everyone but ReiserFS developers and people fine-tuning
|
| /linux-4.1.27/Documentation/video4linux/bttv/ |
| D | README.freeze | 68 fine in theory and many configurations. Neverless it might be worth a
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | ALS | 46 inbuilt MPU401 driver would otherwise be fine). Insert the mpu401 module
|
| D | README.OSS | 1361 The following configuration parameters have worked fine for the PCM12
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | befs.txt | 76 (it is fine to make it a module).
|
| D | ntfs.txt | 234 raid level 5. For striping and mirroring, either driver should work fine.
244 Linear volume sets, i.e. linear raid, has been tested and works fine. Even
385 0, have been tested and work fine (though see section "Limitations when using
|
| D | vfat.txt | 6 No special partition formatter is required. mkdosfs will work fine
|
| D | porting | 345 dcache_lock is gone, replaced by fine grained locks. See fs/dcache.c
|
| D | xfs-delayed-logging-design.txt | 425 written into. While this works just fine for the existing transaction
|
| D | proc.txt | 1395 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
|
| /linux-4.1.27/drivers/auxdisplay/ |
| D | Kconfig | 93 It will work fine. However, you can't attach it to the fbdev driver
|
| /linux-4.1.27/arch/nios2/platform/ |
| D | Kconfig.platform | 104 perfectly fine, even if the Nios II is configured with smaller caches.
|
| /linux-4.1.27/Documentation/power/ |
| D | s2ram.txt | 63 resume it instead works fine.
|
| D | opp.txt | 199 fine grained dynamic control of which sets of OPPs are operationally available.
|
| D | runtime_pm.txt | 659 that the device appears to be runtime-suspended and its state is fine, so it
|
| /linux-4.1.27/Documentation/s390/ |
| D | DASD | 28 an Enterprise Storage Server (Seascape) should work fine as well.
|
| /linux-4.1.27/Documentation/sound/alsa/soc/ |
| D | overview.txt | 21 recording) audio. This is fine for a PC, but tends to waste a lot of
|
| D | DPCM.txt | 334 unless your HW needs more fine grained sequencing of the PCM ops.
|
| /linux-4.1.27/Documentation/ |
| D | parport.txt | 255 If that works fine, try with 'io=0x378 irq=7' (adjust for your
258 If _that_ works fine, then one of the hardware modes isn't working
|
| D | xz.txt | 83 doesn't depend on the dictionary size, and it is perfectly fine to
|
| D | kmemcheck.txt | 137 The default value of 64 is probably fine. If some code produces more
161 The default value should be fine for debugging most problems. It also
182 default value is therefore fine.
208 In fact, this option may also be used for fine-grained control over SLUB vs.
|
| D | email-clients.txt | 177 (a)ttach works fine without "set paste".
|
| D | atomic_ops.txt | 215 fine as well.
626 the cas()) with respect to itself, things will be fine.
|
| D | stable_api_nonsense.txt | 13 just fine on the latest 2.6 kernel release. That interface is the one
|
| D | unaligned-memory-access.txt | 15 For example, reading 4 bytes of data from address 0x10004 is fine, but
|
| D | robust-futexes.txt | 213 All other architectures should build just fine too - but they won't have
|
| D | ManagementStyle | 50 painful ones. Making small and non-consequential decisions is fine, and
|
| D | HOWTO | 238 fine.
|
| D | CodingStyle | 303 u8/u16/u32 are perfectly fine typedefs, although they fit into
|
| D | DMA-API-HOWTO.txt | 325 set the consistent mask even if this default is fine for your
|
| D | pinctrl.txt | 1172 of the type found below. However when doing fine-grained state selection
|
| /linux-4.1.27/Documentation/vm/ |
| D | transhuge.txt | 274 of handling GUP on hugetlbfs will also work fine on transparent
282 at all on hugetlbfs (but it instead works fine on transparent
297 support enabled just fine as always. No difference can be noted in
300 unaffected. libhugetlbfs will also work fine as usual.
|
| D | balance | 31 doing fine even with the presence of this problem. In 2.3, due to
|
| D | unevictable-lru.txt | 425 This is fine, because we'll catch it later if and if vmscan tries to reclaim
|
| /linux-4.1.27/Documentation/x86/i386/ |
| D | IO-APIC.txt | 15 If your box boots fine with enabled IO-APIC IRQs, then your
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-bwc.txt | 62 for more fine-grained consumption.
|
| D | completion.txt | 227 Signaling completion from hard-irq context is fine as it will appropriately
|
| D | sched-design-CFS.txt | 101 chew.c, ring-test.c, massive_intr.c all work fine and do not impact
|
| /linux-4.1.27/tools/perf/config/ |
| D | utilities.mak | 111 # which can handle it just fine).
|
| /linux-4.1.27/drivers/char/agp/ |
| D | Kconfig | 42 This is a hardware limitation. AGP 1x seems to be fine, though.
|
| /linux-4.1.27/drivers/net/can/ |
| D | Kconfig | 48 get started. This works fine for the most common CAN controllers
|
| /linux-4.1.27/Documentation/usb/ |
| D | error-codes.txt | 18 0 URB submission went fine
|
| D | dma.txt | 54 kmalloc() will work just fine.
|
| D | usb-serial.txt | 253 It will be fine with null modem links, as long as you do not try to link two
|
| /linux-4.1.27/kernel/time/ |
| D | Kconfig | 169 The default value will be fine in most cases. Battery-powered
|
| /linux-4.1.27/Documentation/x86/ |
| D | earlyprintk.txt | 116 3. Testing that it works fine:
|
| /linux-4.1.27/Documentation/power/powercap/ |
| D | powercap.txt | 27 fine grained control is required, it can be applied through the subzones.
|
| /linux-4.1.27/Documentation/ia64/ |
| D | serial.txt | 117 Kernel and init script output works fine, but no "login:" prompt:
|
| /linux-4.1.27/arch/parisc/ |
| D | Kconfig | 215 selected (the vast majority of 32bit binaries work perfectly fine
|
| /linux-4.1.27/Documentation/laptops/ |
| D | disk-shock-protection.txt | 97 fine from the occasional buffer under-run incurred by a head park
|
| /linux-4.1.27/drivers/net/ethernet/intel/e1000/ |
| D | e1000_hw.c | 204 u16 fused, fine, coarse; in e1000_phy_init_script() local
216 fine = fused & IGP01E1000_ANALOG_FUSE_FINE_MASK; in e1000_phy_init_script()
224 fine -= IGP01E1000_ANALOG_FUSE_FINE_1; in e1000_phy_init_script()
227 fine -= IGP01E1000_ANALOG_FUSE_FINE_10; in e1000_phy_init_script()
231 (fine & IGP01E1000_ANALOG_FUSE_FINE_MASK) | in e1000_phy_init_script()
|
| /linux-4.1.27/Documentation/networking/ |
| D | arcnet.txt | 59 included and seems to be working fine!
245 NFS: Should be fine linux->linux, just pretend you're using Ethernet cards.
266 Windows: See DOS :) Trumpet Winsock works fine with either the Novell or
|
| D | timestamping.txt | 92 a timestamp is generated at each layer. This allows for fine
358 the requested fine-grained filtering for incoming packets is not
|
| D | eql.txt | 13 source trees. (Yes, it worked fine.)
|
| D | README.sb1000 | 180 7.) Everything seems to work fine but my computer locks up after a while
|
| D | ixgbe.txt | 321 to a Linux-based VM running 2.6.32 or later kernel works fine, there is a
|
| D | z8530drv.txt | 42 driver. If you want to run xNOS instead of our fine kernel AX.25
|
| D | packet_mmap.txt | 37 It's fine to use PACKET_MMAP to improve the performance of the capture and
|
| D | arcnet-hardware.txt | 95 also work fine, because ARCnet is a very stable network. I personally use 75
1198 ARCETHER packet driver loaded fine, but without the red LED
|
| D | can.txt | 1117 Note that this works fine for the most common CAN controllers with
|
| /linux-4.1.27/Documentation/isdn/ |
| D | syncPPP.FAQ | 206 -> fine: your card is dialing and your remote machine
|
| /linux-4.1.27/Documentation/arm/ |
| D | README | 125 The ST506 hard drive controllers seem to be working fine (if a little
|
| /linux-4.1.27/Documentation/dvb/ |
| D | README.dvb-usb | 108 runs fine now
|
| /linux-4.1.27/net/netfilter/ |
| D | Kconfig | 339 fine-grain tuning. This allows you to attach specific timeout
915 problem are that everything works fine from your Linux
919 2) Small mail works fine, but large emails hang.
920 3) ssh works fine, but scp hangs after initial handshaking.
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 150 infrastructure (kdump scripts) to save the dump works fine with
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | compress_offload.txt | 156 difficult to reach with all types of compressed data, but works fine with most
|
| /linux-4.1.27/Documentation/ide/ |
| D | ChangeLog.ide-cd.1994-2004 | 187 * handles resets fine now. <axboe@image.dk>
|
| D | ChangeLog.ide-tape.1995-2002 | 23 * Both configurations seemed to work just fine !
|
| /linux-4.1.27/arch/m68k/ |
| D | Kconfig.cpu | 335 defaults should be fine for most users, but these options may make
|
| /linux-4.1.27/arch/ia64/ |
| D | Kconfig | 272 majority of IA-32 binaries work perfectly fine with a larger page
|
| /linux-4.1.27/drivers/usb/gadget/udc/ |
| D | Kconfig | 298 If unsure, say "N" here. The driver works fine in PIO mode.
|
| /linux-4.1.27/Documentation/hid/ |
| D | hid-transport.txt | 79 running in atomic-context just fine.
|
| /linux-4.1.27/sound/oss/ |
| D | CHANGELOG | 299 - Some fine tuning to the GUS v3.7 mixer code.
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 187 1. If User Mode Linux crashes, your host kernel is still fine.
567 where it will run fine. See ``Compiling the kernel and modules'' if
920 Ethertap is available on 2.4 and works fine. TUN/TAP is preferred
3679 that happened. The rest of the structure looks fine, so this probably
3718 These check out fine.
3742 fine:
|
| /linux-4.1.27/Documentation/kdump/ |
| D | kdump.txt | 462 display work fine.
|
| /linux-4.1.27/Documentation/timers/ |
| D | NO_HZ.txt | 212 gives fine-grained control on exactly which CPUs the
|
| /linux-4.1.27/Documentation/locking/ |
| D | rt-mutex-design.txt | 97 a process being blocked on the mutex, it is fine to allocate
622 is no longer on the list of waiters. This is fine, since the pending owner
|
| /linux-4.1.27/kernel/trace/ |
| D | Kconfig | 556 As it is a tight loop, it benchmarks as hot cache. That's fine because
|
| /linux-4.1.27/mm/ |
| D | Kconfig | 171 Users who don't use the memory hotplug feature are fine with this
|
| /linux-4.1.27/Documentation/filesystems/configfs/ |
| D | configfs.txt | 77 readdir(3) sees this just fine:
|
| /linux-4.1.27/net/sched/ |
| D | Kconfig | 411 fine tuning u32 classifiers.
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci.txt | 611 sequence works fine for I/O Port space:
|
| /linux-4.1.27/Documentation/arm64/ |
| D | arm-acpi.txt | 363 If an SoC vendor wants to provide fine-grained control of the system clocks,
|
| /linux-4.1.27/Documentation/spi/ |
| D | spi-summary | 587 for low-frequency sensor access might be fine using synchronous PIO.
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 2.Process | 470 persistence!) but that's fine - it's a part of kernel development.
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 466 There is no support for more fine grained debug control like
780 Keeping the default should be fine in most cases.
|
| /linux-4.1.27/init/ |
| D | Kconfig | 386 Select this option to enable fine granularity task irq time
1243 major distributions and tools handle this just fine.
|
| /linux-4.1.27/drivers/scsi/ |
| D | Kconfig | 250 will work fine if you say Y here.
958 Generally, saying N is fine.
|
| /linux-4.1.27/scripts/genksyms/ |
| D | parse.tab.c_shipped | 1272 for details. YYERROR is fine as it does not invoke this
|
| /linux-4.1.27/Documentation/m68k/ |
| D | kernel-options.txt | 376 fine enough. This is true for STE, MegaSTE, TT, and Falcon. It is not
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.tab.c_shipped | 1197 for details. YYERROR is fine as it does not invoke this
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-parser.tab.c_shipped | 1099 for details. YYERROR is fine as it does not invoke this
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | cpusets.txt | 491 where it can. It will pick as fine a granularity partition of sched
|
| /linux-4.1.27/arch/x86/ |
| D | Kconfig | 710 Select this option to enable fine granularity task steal time
2171 T400CDT. This is off by default since most machines do fine without
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | README | 132 Samba 3.0) but the CIFS vfs works fine with a wide variety of CIFS servers.
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 382 CDS_DISC_OK& a disc is loaded and everything is fine\cr
|
| /linux-4.1.27/Documentation/RCU/ |
| D | RTFP.txt | 48 providing a fine-grained locking design, however, it would be interesting
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | api.txt | 936 The KVM_SET_MEMORY_REGION does not allow fine grained control over memory
|