Home
last modified time | relevance | path

Searched refs:find (Results 1 – 200 of 503) sorted by relevance

123

/linux-4.1.27/tools/perf/
Dperf-with-kcore.sh121 …find "$USER_HOME/.debug" -xdev -type d ! -user "$SUDO_USER" -ls -exec chown "$SUDO_USE…
122 …find "$USER_HOME/.debug" -xdev -type f -links 1 ! -user "$SUDO_USER" -ls -exec chown "$SUDO_USE…
123 …find "$USER_HOME/.debug" -xdev -type l ! -user "$SUDO_USER" -ls -exec chown -h "$SUDO_USE…
126 …find "$USER_HOME/.debug" -xdev -type d ! -group "$SUDO_GID" -ls -exec chgrp "$SUDO_GID…
127 …find "$USER_HOME/.debug" -xdev -type f -links 1 ! -group "$SUDO_GID" -ls -exec chgrp "$SUDO_GID…
128 …find "$USER_HOME/.debug" -xdev -type l ! -group "$SUDO_GID" -ls -exec chgrp -h "$SUDO_GID…
140 PERMISSIONS_OK+=$(find "$HOME/.debug" -xdev -type d ! -user "$USER" -print -quit)
141 PERMISSIONS_OK+=$(find "$HOME/.debug" -xdev -type f -links 1 ! -user "$USER" -print -quit)
142 PERMISSIONS_OK+=$(find "$HOME/.debug" -xdev -type l ! -user "$USER" -print -quit)
144 PERMISSIONS_OK+=$(find "$HOME/.debug" -xdev -type d ! -group "$GROUPS" -print -quit)
[all …]
DMakefile.perf118 FIND = find
352 $(OUTPUT)perf-read-vdso32: perf-read-vdso.c util/find-vdso-map.c
357 $(OUTPUT)perf-read-vdsox32: perf-read-vdso.c util/find-vdso-map.c
530 $(Q)find . -name '*.o' -delete -o -name '\.*.cmd' -delete -o -name '\.*.d' -delete
DMANIFEST15 tools/include/asm-generic/bitops/find.h
/linux-4.1.27/arch/mn10300/boot/
Dinstall.sh30 for i in `find . -maxdepth 1 -name '*.h' -print`; do
35 for i in `find . -name '*.h' -print`; do
40 for i in `find . -name '*.h' -print`; do
45 for i in `find . -name '*.h' -print`; do
50 for i in `find . -name '*.h' -print`; do
55 for i in `find . -name '*.h' -print`; do
60 for i in `find . -name '*.h' -print`; do
65 for i in `find . -name '*.h' -print`; do
/linux-4.1.27/scripts/
Dtags.sh53 find ${tree}arch/$1 $ignore $subarchprune $prune -name "$2" \
60 include=$(find ${tree}arch/$1/ $subarchprune \
64 find $include $ignore -name "$2" -not -type l -print;
71 find ${tree}include $ignore -name config -prune -o -name "$1" \
79 find ${tree}* $ignore \
297 subarchdir=$(find ${tree}arch/$SRCARCH/ -name "mach-*" -type d -o \
Dpatch-kernel161 find $sourcedir/ '(' -name '*.orig' -o -name '.*.orig' ')' -exec rm -f {} \;
183 find $sourcedir/ '(' -name '*.orig' -o -name '.*.orig' ')' -exec rm -f {} \;
Dgen_initramfs_list.sh92 my_mtime=$(find "$1" -printf "%T@\n" | sort -r | head -n 1)
174 dirlist=$(find "${srcdir}" -printf "%p %m %U %G\n")
Dobjdiff80 for f in $(find $d -name '*.o')
Dshow_delta114 if string.find(rest, base_str)==1:
Dcoccicheck174 for f in `find $srctree/scripts/coccinelle/ -name '*.cocci' -type f | sort`; do
DMakefile.modpost63 MODLISTCMD := find $(MODVERDIR) -name '*.mod' | xargs -r grep -h '\.ko$$' | sort -u
Dnamespace.pl145 &find(\&linux_objects, '.'); # find the objects and do_nm on them
/linux-4.1.27/drivers/staging/rtl8723au/
DTODO2 - find and remove code valid only for 5 HGz. Many of the obvious
4 - find and remove any code for other chips that is left over
6 - find codes that can use %pM and %Nph formatting
/linux-4.1.27/drivers/staging/rtl8188eu/
DTODO2 - find and remove remaining code valid only for 5 HGz. Most of the obvious
4 - find and remove any code for other chips that is left over
6 - find codes that can use %pM and %Nph formatting
/linux-4.1.27/drivers/pinctrl/mediatek/
Dpinctrl-mt8173.c125 bool find = false; in spec_pull_set() local
129 find = true; in spec_pull_set()
134 if (!find) in spec_pull_set()
229 bool find = false; in spec_ies_smt_set() local
234 find = true; in spec_ies_smt_set()
239 if (!find) in spec_ies_smt_set()
Dpinctrl-mt8135.c247 bool find = false; in spec_pull_set() local
251 find = true; in spec_pull_set()
256 if (!find) in spec_pull_set()
/linux-4.1.27/Documentation/laptops/
Dsony-laptop.txt15 subsystem. See the logs of /proc/bus/input/devices to find out what those
27 If your laptop model supports it, you will find sysfs files in the
78 such a laptop you will find the necessary rfkill devices under
93 In your kernel logs you will find the list of all ACPI methods
99 (2) SN00 is used to find values in the lookup table
122 files and find out what is the impact on your laptop.
124 Should you find anything interesting, please report it back to me,
/linux-4.1.27/drivers/xen/xen-pciback/
Dpciback.h99 int (*find)(struct pci_dev *pcidev, struct xen_pcibk_device *pdev, member
154 if (xen_pcibk_backend && xen_pcibk_backend->find) in xen_pcibk_get_pcifront_dev()
155 return xen_pcibk_backend->find(pcidev, pdev, domain, bus, in xen_pcibk_get_pcifront_dev()
Dpassthrough.c191 .find = __xen_pcibk_get_pcifront_dev,
Dvpci.c265 .find = __xen_pcibk_get_pcifront_dev,
/linux-4.1.27/include/linux/
Dtextsearch.h42 unsigned int (*find)(struct ts_config *, member
107 unsigned int ret = conf->ops->find(conf, state); in textsearch_next()
/linux-4.1.27/Documentation/filesystems/nfs/
DExporting20 string for any dentry, and how to find an appropriate dentry for any
111 to find or create a dentry for the same object. The default
117 Given a filehandle fragment, this should find the implied object and
121 Given a filehandle fragment, this should find the parent of the
134 When given a parent dentry and a child dentry, this should find a name
138 to find potential names, and matches inode numbers to find the correct
Drpc-cache.txt86 cache_parse should parse this, find the item in the
98 To find a value in a cache, call sunrpc_cache_lookup passing a pointer
180 added to the channel but instead all lookups that do not find a valid
Dfault_injection.txt6 can help the developer find and fix bugs before their code is shipped in a
Didmapper.txt54 request-key will find the first matching line and corresponding program. In
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-devices12 this. If a program wishes to find different things in
17 devices being added and removed from this tree to find
Dsysfs-fs-ext423 will search to find the best extent
30 will search to find the best extent
Dsysfs-fs-f2fs64 Controls the number of trials to find a victim segment.
Dsysfs-driver-ppi9 'find /sys/ -name 'pcrs''. For the detail information of PPI,
Dsysfs-wusb_cbaf34 - If the CDID is zero (or the CM doesn't find a
Dsysfs-class-net-mesh108 uses to find the optimal paths through the mesh.
/linux-4.1.27/Documentation/networking/
Dfib_trie.txt120 trie, key segment by key segment, until we find a leaf. check_leaf() does
123 If we find a match, we are done.
125 If we don't find a match, we enter prefix matching mode. The prefix length,
127 and we backtrack upwards through the trie trying to find a longest matching
133 the child index until we find a match or the child index consists of nothing but
137 chop off part of the key in order to find the longest matching prefix.
Dnetconsole.txt146 TIP: to find out the MAC address of, say, 10.0.0.2, you may try using:
152 default gateway (you may use /sbin/route -n to find it out) as the
160 NOTE: if you find that the remote logging agent is not receiving or
Ddns_resolver.txt77 it doesn't find it, it upcalls to userspace to make a new DNS query, which
126 keyrings for a cached DNS result. If that fails to find one, it upcalls to
Dmac80211-injection.txt63 You can also find a link to a complete inject application here:
Dbaycom.txt144 interface at a time. The serial driver grabs all interfaces it can find at
146 access a serial port. You might therefore find it necessary to release
Dnetdev-FAQ.txt30 You can find the trees here:
107 Q: The above only says "Under Review". How can I find out more?
128 A quick way to find whether the patch is in this stable-queue is
Dtproxy.txt51 be able to find out the original destination address. Even in case of TCP
/linux-4.1.27/Documentation/sound/oss/
DREADME.modules20 If you don't set these, you will probably find you can play .wav files
52 options. To find the filename of the driver, look in
82 possible that we can't find a large enough free block in this region after
97 unnecessary. It is possible that machine with 16MB or less RAM will find
99 cannot find a 64K block free, you will be wasting even more RAM by keeping
DVIBRA1623 The only inconvenient you may find is that you will have
/linux-4.1.27/tools/lib/lockdep/
DMakefile127 find . -name '*.[ch]' | xargs ctags --extra=+f --c-kinds=+px \
132 find . -name '*.[ch]' | xargs etags \
/linux-4.1.27/Documentation/arm/sunxi/
Dclocks.txt49 you can find it at
54 released by Allwinner, you can find it at
/linux-4.1.27/Documentation/
Dinit.txt28 to find out which libraries are required.
36 To find out more, add code to init/main.c to display kernel_execve()s
39 Please extend this explanation whenever you find new failure causes
Dgcov.txt221 find $KSRC $KOBJ \( -name '*.gcno' -o -name '*.[ch]' -o -type l \) -a \
250 find $GCDA -type d -exec mkdir -p $TEMPDIR/\{\} \;
251 find $GCDA -name '*.gcda' -exec sh -c 'cat < $0 > '$TEMPDIR'/$0' {} \;
252 find $GCDA -name '*.gcno' -exec sh -c 'cp -d $0 '$TEMPDIR'/$0' {} \;
DBUG-HUNTING23 Finding bugs is not always easy. Have a go though. If you can't find it don't
90 find dir -name '*.[oa]' -print | xargs rm -f
129 Then recompile, retest, move the ifdefs until you find the one
153 output to find the valid line of code/assembler. Without debug symbols, you
Dbt8xxgpio.txt14 find them used for low prices on the net.
Dkmemcheck.txt33 programmer errors that the compiler is not able to find through static
220 positive warnings to appear. Therefore, try not to use this. If you find that
393 and find that this is indeed where items are being added to the list:
567 really the number 0x00000080. With a bit of research, we find that this is
631 Now, even though we didn't find an actual error here, the example is still a
632 good one, because it shows how one would go about to find out what the report
651 ability to find (real) errors in other parts of the same struct.
698 maintainers. Instead, I encourage maintainers and developers to find errors
706 false positives that we can annotate and silence. So whatever you find,
Doops-tracing.txt36 may find that booting with a higher resolution (eg, vga=791)
69 That's the easy way to find the problem, at least if the bug-report is
121 Then you need to find out _why_ they don't match. Often it's simple - you
161 must be able to find a system map file at daemon initialization time.
Dsysfs-rules.txt137 "device"-link to find the parent devices in /sys/devices/. That is the
147 may be used to find the child devices in /sys/class. That is the single
160 by its subsystem value. You need to walk up the chain until you find
Dstable_api_nonsense.txt96 stopping to slow down. As such, the kernel developers find bugs in
172 - Other people will find and fix bugs in your driver.
173 - Other people will find tuning opportunities in your driver.
Diostats.txt45 find just the eleven fields, beginning with 446216. If you look at
58 system-wide stats you'll have to find all the devices and sum them all up.
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/cpm/
Di2c.txt16 i2c drivers to find the bus to probe:
20 by legacy i2c device drivers to find a bus in a specific context like
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/engine/disp/
Doutp.c90 outp->port = i2c->find(i2c, NV_I2C_PORT(outp->info.i2c_index)); in nvkm_output_create_()
92 outp->port = i2c->find(i2c, NV_I2C_AUX(outp->info.i2c_index)); in nvkm_output_create_()
Dconn.c122 ret = gpio->find(gpio, 0, info->hpd, DCB_GPIO_UNUSED, &func); in nvkm_connector_create_()
/linux-4.1.27/arch/s390/lib/
DMakefile5 lib-y += delay.o string.o uaccess.o find.o
/linux-4.1.27/arch/alpha/lib/
Dstxncpy.S85 negq t8, t12 # e0 : find low bit set
122 and a0, 7, t0 # .. e1 : find dest misalignment
174 cmpbge zero, t2, t8 # e0 : find nulls in second partial
294 and a0, 7, t4 # .. e1 : find dest misalignment
295 and a1, 7, t5 # e0 : find src misalignment
Dev6-stxncpy.S112 negq t8, t12 # E : find low bit set
154 and a0, 7, t0 # E : find dest misalignment
216 cmpbge zero, t2, t8 # E : find nulls in second partial
339 and a0, 7, t4 # E : find dest misalignment
340 and a1, 7, t5 # E : find src misalignment
Dstxcpy.S72 negq t8, t6 # e0 : find low bit set
237 and a0, 7, t4 # .. e1 : find dest misalignment
238 and a1, 7, t5 # e0 : find src misalignment
Dev6-stxcpy.S88 negq t8, t6 # E : find low bit set
267 and a0, 7, t4 # E : find dest misalignment
268 and a1, 7, t5 # E : find src misalignment
Dclear_user.S83 and $6, 7, $4 # e0 : find dest misalignment
Dmemchr.S46 # below when we find the address of the last byte. Given
Dev6-clear_user.S65 and $6, 7, $4 # .. E .. .. : find dest head misalignment
Dev6-memchr.S43 # below when we find the address of the last byte. Given
/linux-4.1.27/Documentation/parisc/
Ddebugging17 an HPMC instead of a kernel oops. To debug an HPMC, try to find
33 registers interruption handlers read to find out where the machine
/linux-4.1.27/arch/arm/mach-orion5x/include/mach/
Dentry-macro.S21 @ find cause bits that are unmasked
/linux-4.1.27/tools/build/tests/ex/
DMakefile20 find . -name '*.o' -delete -o -name '\.*.cmd' -delete -o -name '\.*.d' -delete
/linux-4.1.27/tools/lib/traceevent/
DMakefile220 find . -name '*.[ch]' | xargs ctags --extra=+f --c-kinds=+px \
225 find . -name '*.[ch]' | xargs etags \
/linux-4.1.27/fs/ubifs/
DMakefile5 ubifs-y += budget.o find.o tnc_commit.o compress.o lpt.o lprops.o
/linux-4.1.27/drivers/gpu/drm/nouveau/include/nvkm/subdev/
Dgpio.h27 int (*find)(struct nvkm_gpio *, int idx, u8 tag, u8 line, member
Di2c.h65 struct nvkm_i2c_port *(*find)(struct nvkm_i2c *, u8 index); member
/linux-4.1.27/arch/arm/mach-dove/include/mach/
Dentry-macro.S30 @ find first active interrupt source
/linux-4.1.27/Documentation/vm/
Dpagemap.txt10 * /proc/pid/pagemap. This file lets a userspace process find out which
139 The general procedure for using pagemap to find out about a process' memory
151 For example, to find the "unique set size" (USS), which is the amount of
153 you can go through every map in the process, find the PFNs, look those up
Dsoft-dirty.txt40 can find more details about it on http://criu.org
/linux-4.1.27/Documentation/input/
Dcd32.txt4 find it useful).
Dyealink.txt40 find the sysfs files.
42 distributions you can do: "find /sys/ -name get_icons" for a hint.
Dbcm5974.txt38 with the HID driver, which, if not told otherwise, will find the standard
Dedt-ft5x06.txt33 you'll find the following files:
/linux-4.1.27/Documentation/devicetree/bindings/usb/
Disp1301.txt8 - transceiver: phandle of isp1301 - this helps the ISP1301 driver to find the
/linux-4.1.27/tools/testing/selftests/powerpc/
DMakefile51 find . -name '*.c' -o -name '*.h' | xargs ctags
/linux-4.1.27/drivers/lguest/
DMakefile18 @sh ../../tools/lguest/extract $(PREFIX) `find ../../* -name '*.[chS]' -wholename '*lguest*'`
/linux-4.1.27/arch/arm/mach-mv78xx0/include/mach/
Dentry-macro.S38 @ find first active interrupt source
/linux-4.1.27/Documentation/RCU/
Drcu.txt70 "read-copy update" to find it.
75 search for the string "Patent" in RTFP.txt to find them.
89 o Where can I find more information on RCU?
Drcuref.txt110 search_and_reference() cannot find this element, which means that the value
/linux-4.1.27/tools/testing/selftests/rcutorture/bin/
Dkvm-recheck.sh32 dirs=`find $rd -name Make.defconfig.out -print | sort | sed -e 's,/[^/]*$,,' | sort -u`
/linux-4.1.27/Documentation/blockdev/drbd/
DREADME.txt8 Please visit http://www.drbd.org to find out more.
/linux-4.1.27/arch/m32r/
DKconfig.debug10 This results in a large slowdown, but helps to find certain types
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/volt/
Dgpio.c85 int ret = gpio->find(gpio, 0, tags[i], 0xff, &func); in nvkm_voltgpio_init()
/linux-4.1.27/Documentation/sysctl/
Dabi.txt11 You can find further details about abi in include/linux/personality.h.
/linux-4.1.27/tools/lib/api/
DMakefile39 find $(if $(OUTPUT),$(OUTPUT),.) -name \*.o | xargs $(RM)
/linux-4.1.27/arch/frv/mm/
Dtlb-flush.S61 # find out how many lines there are
102 # find out how many lines there are
/linux-4.1.27/drivers/char/xillybus/
DKconfig29 Set to M if you want Xillybus to find its resources from the
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/i2c/
Dbase.c328 struct nvkm_i2c_port *port = i2c->find(i2c, index); in nvkm_i2c_intr_fini()
338 struct nvkm_i2c_port *port = i2c->find(i2c, index); in nvkm_i2c_intr_init()
528 i2c->find = nvkm_i2c_find; in nvkm_i2c_create_()
590 parent = nv_object(i2c->find(i2c, outp.i2c_index)); in nvkm_i2c_create_()
/linux-4.1.27/Documentation/power/
Dbasic-pm-debugging.txt41 To find out why hibernation fails on your system, you can use a special testing
109 after the test, so please take that into consideration). To find this driver,
156 find it by loading a half of the modules you normally use and binary searching
164 Again, if you find the offending module(s), it(they) must be unloaded every time
172 techniques to find the problem. First, if there is a serial port in your box,
203 analogous to the one described in section 1. If you find some failing drivers,
Dtricks.txt26 When you make it work, try to find out what exactly was it that broke
Dopp.txt72 dev_pm_opp_find_freq_exact is meant to be used to find the opp pointer which can then
145 find the OPP prior to call the dev_pm_opp_enable to actually make it available.
164 Example: To find the highest opp for a device:
174 Example 1: To find the lowest opp for a device:
/linux-4.1.27/Documentation/isdn/
DREADME.FAQ6 You find it in:
/linux-4.1.27/scripts/coccinelle/null/
Dbadzero.cocci96 try let _ = Hashtbl.find negtable f in ()
116 try let _ = Hashtbl.find negtable f in ()
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/therm/
Dfan.c237 ret = gpio->find(gpio, 0, DCB_GPIO_FAN, 0xff, &func); in nvkm_therm_fan_ctor()
263 ret = gpio->find(gpio, 0, DCB_GPIO_FAN_SENSE, 0xff, &priv->fan->tach); in nvkm_therm_fan_ctor()
/linux-4.1.27/scripts/coccinelle/misc/
Dbugon.cocci3 //# This makes an effort to find cases where BUG() follows an if
Darray_size.cocci3 //# This makes an effort to find cases where ARRAY_SIZE can be used such as
Dbadty.cocci3 //# This makes an effort to find cases where the argument to sizeof is wrong
/linux-4.1.27/mm/
DKconfig.debug19 This results in a large slowdown, but helps to find certain types
/linux-4.1.27/Documentation/aoe/
Dudev.txt8 # bash# find /etc -type f -name udev.conf
Daoe.txt27 Users of udev should find the block device nodes created
51 "echo > /dev/etherd/discover" tells the driver to find out what AoE
/linux-4.1.27/Documentation/devicetree/bindings/clock/
Dvf610-clock.txt10 given clock controller. Please refer the next section to find
Dexynos7-clock.txt47 find the input clocks for a given controller.
/linux-4.1.27/Documentation/ko_KR/
Dstable_api_nonsense.txt5 If you find any difference between this document and the original file or
/linux-4.1.27/Documentation/acpi/
Dinitrd_table_override.txt32 Complain to your platform/BIOS vendor if you find a bug which is so sever
70 find kernel | cpio -H newc --create > /boot/instrumented_initrd
/linux-4.1.27/Documentation/x86/
Dearlyprintk.txt57 You can find the physical port through experimentation by trying
64 physical connector and if you find such a device send a complaint
114 and find out which port has debug device connected.
Dearly-microcode.txt40 find . | cpio -o -H newc >../ucode.cpio
/linux-4.1.27/scripts/coccinelle/api/alloc/
Dalloc_cast.cocci4 //# This makes an effort to find cases of casting of values returned by
/linux-4.1.27/arch/m68k/fpsp040/
Dsgetem.S120 bfffo %d0{#0:#32},%d3 |find first 1 in ls mant to d0
127 bfffo %d0{#0:#32},%d3 |find first 1 in ls mant to d0
/linux-4.1.27/drivers/staging/media/bcm2048/
DTODO8 find many examples of how to do this in drivers/media/radio.
/linux-4.1.27/tools/perf/scripts/python/
Dnetdev-times.py61 if dev != 0 and hunk['dev'].find(dev) < 0:
92 if irq_list[i]['name'].find(dev) >= 0:
164 elif arg.find('dev=',0, 4) >= 0:
/linux-4.1.27/security/tomoyo/
Dutil.c392 bool tomoyo_str_starts(char **src, const char *find) in tomoyo_str_starts() argument
394 const int len = strlen(find); in tomoyo_str_starts()
397 if (strncmp(tmp, find, len)) in tomoyo_str_starts()
Dcommon.c545 static s8 tomoyo_find_yesno(const char *string, const char *find) in tomoyo_find_yesno() argument
547 const char *cp = strstr(string, find); in tomoyo_find_yesno()
549 cp += strlen(find); in tomoyo_find_yesno()
568 const char *find) in tomoyo_set_uint() argument
570 const char *cp = strstr(string, find); in tomoyo_set_uint()
572 sscanf(cp + strlen(find), "=%u", i); in tomoyo_set_uint()
/linux-4.1.27/Documentation/trace/
Devents-nmi.txt22 specifically. You need to find its address:
/linux-4.1.27/Documentation/ja_JP/
Dstable_kernel_rules.txt5 If you find difference with original file or problem in translation,
Dstable_api_nonsense.txt5 If you find any difference between this document and the original file
DSubmitChecklist5 If you find any difference between this document and the original file
/linux-4.1.27/Documentation/driver-model/
Dbinding.txt26 to find one that supports it. In order to determine that, the device
82 The bus's list of devices is iterated over to find a match. Devices
/linux-4.1.27/Documentation/timers/
Dtimekeeping.txt9 If you grep through the kernel source you will find a number of architecture-
58 multiply and shift, so in clocksource_cyc2ns() you find:
62 You will find a number of helper functions in the clock source code intended
101 arithmetic, and you find the same family of helper functions again for
/linux-4.1.27/Documentation/ABI/stable/
Dvdso12 To find the DSO, parse the auxiliary vector passed to the program's
/linux-4.1.27/lib/
Dtextsearch.c146 if (ops->name == NULL || ops->find == NULL || ops->init == NULL || in textsearch_register()
Dts_kmp.c136 .find = kmp_find,
DKconfig.kasan12 designed to find out-of-bounds accesses and use-after-free bugs.
Dts_bm.c186 .find = bm_find,
/linux-4.1.27/Documentation/scheduler/
Dsched-stats.txt83 not find a busier queue while the cpu was idle
99 find a busier queue while the cpu was busy
115 find a busier queue while the cpu was just becoming idle
/linux-4.1.27/Documentation/fb/
Dsstfb.txt61 cat /proc/fb. You can find a copy of con2fb in tools/ directory.
118 find some of these interesting :
146 - I didn't really test changing the palette, so you may find some weird
/linux-4.1.27/net/decnet/
DKconfig12 To find some tools to use with the kernel layer support, please
/linux-4.1.27/Documentation/devicetree/bindings/phy/
Dphy-bindings.txt10 provider can use the values in cells to find the appropriate
/linux-4.1.27/Documentation/xtensa/
Datomctl.txt30 Developers might find using RCW in Bypass mode convenient when testing
/linux-4.1.27/Documentation/devicetree/bindings/clock/st/
Dst,clkgen.txt6 We will find only the base address of the Clockgen, this base
Dst,flexgen.txt10 Please find an example below:
/linux-4.1.27/tools/testing/selftests/rcutorture/doc/
Drcu-test-image.txt38 …http://www.moe.co.uk/2011/01/07/pci_add_option_rom-failed-to-find-romfile-pxe-rtl8139-bin/ -- "apt…
/linux-4.1.27/Documentation/block/
Dswitching-sched.txt6 tunables control how the io scheduler works. You can find these entries
/linux-4.1.27/Documentation/x86/i386/
DIO-APIC.txt100 Generally, it's always possible to find out the correct pirq= settings, just
112 Use smart trial-and-error techniques to find out the correct pirq line ...
/linux-4.1.27/drivers/spi/
Dspi-s3c24xx-fiq.S28 @ fiq_rirq The base of the IRQ registers to find S3C2410_SRCPND
/linux-4.1.27/tools/testing/selftests/ftrace/
Dftracetest41 echo `find $1 -name \*.tc | sort`
/linux-4.1.27/Documentation/devicetree/bindings/media/
Dti,omap3isp.txt23 respectively. Please find more information on common
/linux-4.1.27/
DREPORTING-BUGS45 To find out where to send an emailed bug report, find your subsystem or
96 overlook things, and easier for the developers to find the pieces of
DMakefile1026 $(Q)find $(srctree)/include/ -name '*.h' | xargs --max-args 1 \
1218 @find $(srctree) $(RCS_FIND_IGNORE) \
1431 @find $(if $(KBUILD_EXTMOD), $(KBUILD_EXTMOD), .) $(RCS_FIND_IGNORE) \
1454 find $(srctree)/* $(RCS_FIND_IGNORE) \
1459 find $(srctree)/* $(RCS_FIND_IGNORE) \
1487 $(OBJDUMP) -d vmlinux $$(find . -name '*.ko') | \
DREADME223 You can find more information on using the Linux kernel config tools
245 break bad code to find kernel problems (kmalloc()). Thus you
368 To find out the kernel function name, you'll need to find the system
376 order, from which it is simple to find the function that contains the
383 is followed by a function with a higher address you will find the one
/linux-4.1.27/drivers/gpu/drm/nouveau/dispnv04/
Ddisp.c104 nv_encoder->i2c = i2c->find(i2c, nv_encoder->dcb->i2c_index); in nv04_display_create()
Dtvnv04.c208 struct nvkm_i2c_port *port = i2c->find(i2c, entry->i2c_index); in nv04_tv_create()
/linux-4.1.27/Documentation/mtd/
Dspi-nor.txt13 find the right LUT sequence. Unfortunately, the SPI subsystem has no notion of
/linux-4.1.27/tools/power/acpi/
DMakefile144 -find $(OUTPUT) \( -not -type d \) -and \( -name '*~' -o -name '*.[oas]' \) -type f -print \
/linux-4.1.27/arch/um/
DMakefile143 @find . \( -name '*.bb' -o -name '*.bbg' -o -name '*.da' \
/linux-4.1.27/Documentation/hwmon/
Dpc8742757 not. I couldn't find a way to figure out the external sensor data
Dlm7857 It is a value in volts. When it is unconnected, you will often find the
/linux-4.1.27/Documentation/scsi/
Dbfa.txt69 and use the following inbox and out-of-box driver version mapping to find
/linux-4.1.27/drivers/net/plip/
DKconfig22 time (mode 1); you can find the wiring of these cables in
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DGPIO.txt8 manipulate the state of the GPIO pins, and find out other
13 data-sheet/users manual to find out the complete list.
/linux-4.1.27/Documentation/arm/Samsung/
DOverview.txt9 the current kernel support, how to use it and where to find the code
/linux-4.1.27/Documentation/arm/SA1100/
DItsy36 the itsy. (i.e. grep for CONFIG_SA1100_ITSY and you'll find where it is.)
/linux-4.1.27/drivers/staging/iio/Documentation/
Dinkernel.txt21 This are then used to find the channel mapping from the consumer device (see
/linux-4.1.27/drivers/staging/speakup/
DTODO36 This bug happens regularly, but no one has been able to find a situation
/linux-4.1.27/arch/ia64/
DMakefile38 a source-tree that post-dates 18-Dec-2002. You can find a pre-compiled \
/linux-4.1.27/Documentation/video4linux/
Dfimc.txt133 How to find out which /dev/video? or /dev/v4l-subdev? is assigned to which
136 You can either grep through the kernel log to find relevant information, i.e.
DREADME.cx8857 * the tuner type used by the card. You can try to find one by
/linux-4.1.27/drivers/parport/
DKconfig74 FIFO. See <file:Documentation/parport.txt> to find out how to
82 find out things like base addresses, IRQ lines and DMA channels. It
/linux-4.1.27/Documentation/filesystems/
Dbfs.txt35 To create the BFS image under UnixWare you need to find out first which
Dntfs.txt70 time find . -type f -exec md5sum "{}" \;
220 problems with this approach so far. If you find a problem with this, please
277 will find the precompiled (i386) ldminfo utility there. NOTE: You will not be
290 section). You can then find these Disk Ids in the VBLK DATABASE section in the
419 different available algorithms until you find one that works. Make sure you
421 otherwise. If you find which algorithm works please let us know (email the
Dramfs-rootfs-initramfs.txt121 free up the space (find -xdev / -exec rm '{}' ';'), overmount rootfs
160 two example "file" entries expect to find files named "init.sh" and "busybox" in
199 (cd "$1"; find . | cpio -o -H newc | gzip) > "$2"
207 of filenames is with the find command; you should give find the -depth option
Dcramfs.txt33 no need to use -noleaf in `find', btw.)
Dpath-lookup.txt47 Name lookups will want to find a particular path that a name string refers to
67 - find the start point of the walk;
167 find either 'A' or 'B'. So if a lookup of 'A' returns NULL, a subsequent lookup
171 hash list, a lookup may find neither 'A' nor 'B' matching the dentry. The same
253 +---------------------+ ... which brings us here. We find dentry1 via
/linux-4.1.27/Documentation/devicetree/bindings/i2c/
Di2c-pxa-pci-ce4100.txt11 number to its physical address and to use this to find the child nodes
/linux-4.1.27/Documentation/video4linux/cx2341x/
Dfw-upload.txt3 How to find
/linux-4.1.27/Documentation/watchdog/
Dpcwd-watchdog.txt17 The Watchdog Driver will automatically find your watchdog card, and will
Dconvert_drivers_to_kernel_api.txt115 All possible callbacks are defined in 'struct watchdog_ops'. You can find it
117 owner must be set, the rest are optional. You will easily find corresponding
/linux-4.1.27/Documentation/wimax/
DREADME.i2400m134 To find which parameters are supported by a module, run:
170 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
216 Thus, to find the average buffer size received, divide accumulated
DREADME.wimax59 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
/linux-4.1.27/Documentation/i2c/busses/
Di2c-i801120 /proc/acpi/thermal_zone. If you find anything there, it's likely that
143 (Asus) and the subdevice ID is 80f2 (P4P800-X). You can find the symbolic
/linux-4.1.27/Documentation/usb/
Dusbmon.txt45 buses), and skip to step #3, or find the bus used by your device with step #2.
50 Run "cat /sys/kernel/debug/usb/devices", and find the T-line which corresponds
146 present because it is never a number. Thus if scripts find a set of numbers
148 If they find something else, like a letter, they read the setup packet before
Dchipidea.txt91 for i in $(find /sys -name wakeup | grep usb);do echo enabled > $i;done;
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/mxm/
Dbase.c54 port = i2c->find(i2c, i2cidx); in mxm_shadow_rom()
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Dkernel.fuc348 // find out how much time elapsed since the last update
435 find:
461 call(find)
/linux-4.1.27/arch/xtensa/kernel/
Dvectors.S79 addx4 a0, a0, a3 # find entry in table
106 addx4 a0, a0, a3 # find entry in table
Dalign.S475 addx4 a0, a0, a3 # find entry in table
481 addx4 a0, a0, a3 # find entry in table
/linux-4.1.27/fs/cramfs/
DREADME29 lines); put another way, the same order as `find -type d -exec
53 tree, i.e. the same order as `find -size +0 \( -type f -o -type l \)
/linux-4.1.27/Documentation/development-process/
D4.Coding83 On the other hand, if you find yourself copying significant amounts of code
244 - DEBUG_SLAB can find a variety of memory allocation and use errors; it
247 - DEBUG_SPINLOCK, DEBUG_ATOMIC_SLEEP, and DEBUG_MUTEXES will find a
261 lockdep can find a number of scenarios in which the system could, on rare
293 The "Coccinelle" tool (http://coccinelle.lip6.fr/) is able to find a wide
372 the need arises. If you find yourself having to work around a kernel API,
/linux-4.1.27/security/keys/
DKconfig14 support and the like can find them.
/linux-4.1.27/Documentation/thermal/
Dnouveau_thermal16 cannot access any of the i2c external monitoring chips it may find. If you
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/subdev/gpio/
Dbase.c223 gpio->find = nvkm_gpio_find; in nvkm_gpio_create_()
/linux-4.1.27/arch/arm/mm/
Dcache-v7.S144 ands r4, r4, r1, lsr #3 @ find maximum number on the way size
145 clz r5, r4 @ find bit position of way size increment
/linux-4.1.27/Documentation/serial/
Drocket.txt95 Before installing RocketPort(R) or RocketPort RA boards, you must find
120 RocketPort cards. Below, you will find a list of commonly used I/O
Dmoxa-smartio79 In Moxa's Web sites, you may always find latest driver at http://www.moxa.com/.
156 You may find all the driver and utilities files in /moxa/mxser.
407 In /proc/devices, you may find all the major numbers occupied
496 which device causes the situation, please check /proc/interrupts to find
/linux-4.1.27/arch/arm/mach-shmobile/
Dclock-r8a7740.c405 goto find; in hdmi12_set_rate()
408 find: in hdmi12_set_rate()
/linux-4.1.27/drivers/mtd/
DKconfig211 You may find that the algorithms used in this code are patented
228 You may find that the algorithms used in this code are patented
253 You may find that the algorithms used in this code are patented
/linux-4.1.27/drivers/net/wireless/iwlegacy/
DKconfig85 You can find the list of debug mask values in:
/linux-4.1.27/arch/c6x/lib/
Ddivremu.S22 ;; We use a series of up to 31 subc instructions. First, we find
/linux-4.1.27/Documentation/DocBook/
DMakefile59 find $(obj)/man -name '*.9' | xargs gzip -f
/linux-4.1.27/drivers/scsi/aic7xxx/
DKconfig.aic79xx75 variable ahd_debug in that file to find them.
DKconfig.aic7xxx80 variable ahc_debug in that file to find them.
/linux-4.1.27/Documentation/s390/
D3270.txt157 to find out. Probably it isn't. Try loading it manually, with
162 above? Use the grep command to find out; for instance, issue
167 step 2 above? Use the ls -l command to find out; for instance,
/linux-4.1.27/Documentation/fmc/
Didentifiers.txt54 The "Official Name" above is what you find in the FRU official
62 soon as I find some time for that.
/linux-4.1.27/Documentation/pps/
Dpps.txt140 inside you find several files:
145 Inside each "assert" and "clear" file you can find the timestamp and a
/linux-4.1.27/Documentation/devicetree/bindings/video/
Dsimple-framebuffer.txt35 information to find the right node. In that case an extra platform specific
/linux-4.1.27/Documentation/video4linux/bttv/
DREADME.freeze19 With a hard freeze you probably doesn't find anything in the logfiles.
/linux-4.1.27/fs/ntfs/
DKconfig60 so you may find that some very small files (<500 bytes or so) cannot

123