Home
last modified time | relevance | path

Searched refs:find (Results 1 – 25 of 27) sorted by relevance

12

/drivers/acpi/
Dglue.c97 struct acpi_find_child *find = context; in do_acpi_find_child() local
102 if (info->address == find->address) in do_acpi_find_child()
103 find->handle = handle; in do_acpi_find_child()
111 struct acpi_find_child find = { NULL, address }; in acpi_get_child() local
116 1, do_acpi_find_child, &find, NULL); in acpi_get_child()
117 return find.handle; in acpi_get_child()
/drivers/media/video/pwc/
Dpwc-misc.c43 int i, find; in pwc_decode_size() local
70 find = -1; in pwc_decode_size()
74 find = i; in pwc_decode_size()
77 return find; in pwc_decode_size()
/drivers/lguest/
DMakefile21 …@sh ../../Documentation/lguest/extract $(PREFIX) `find ../../* -name '*.[chS]' -wholename '*lguest…
/drivers/staging/otus/
DKconfig16 wpa_supplicant 0.4.8. For your convenience you can find the
/drivers/xen/
DKconfig37 The old xenstore userspace tools expect to find "xenbus"
/drivers/net/wireless/iwlwifi/
DKconfig39 You can find the list of debug mask values in:
171 You can find the list of debug mask values in:
/drivers/parport/
DKconfig69 FIFO. See <file:Documentation/parport.txt> to find out how to
77 find out things like base addresses, IRQ lines and DMA channels. It
/drivers/mtd/
DKconfig238 You may find that the algorithms used in this code are patented
255 You may find that the algorithms used in this code are patented
280 You may find that the algorithms used in this code are patented
/drivers/staging/asus_oled/
DREADME15 in my case, and I hope others will find it useful too!
37 If it doesn't find your display, you can try removing usbhid module.
/drivers/scsi/aic7xxx/
DKconfig.aic79xx76 variable ahd_debug in that file to find them.
DKconfig.aic7xxx81 variable ahc_debug in that file to find them.
Daic7xxx.seq1805 * that the reconnection is for - find the correct SCB and switch to it,
1806 * clearing the "disconnected" bit so we don't "find" it by accident later.
1874 * If we get one, we use the tag returned to find the proper
2069 * We didn't find it. Page in the SCB.
Daic79xx.seq557 * to find the last SCB that was sent correctly.
1109 * If we get one, we use the tag returned to find the proper
/drivers/net/wireless/b43/
DKconfig115 Say Y, if you want to find out why the driver does not
/drivers/message/i2o/
DKconfig81 is to rescan the bus to find new devices.
/drivers/usb/serial/
DChangeLog.history164 Cleaned up debugging statements in a quest to find UHCI timeout bug.
265 now it looks to find a continuous space for the new device.
478 Cleaned up debugging statements in a quest to find UHCI timeout bug.
559 find a way to work arount this UHCI bug )
/drivers/base/
DKconfig51 into the kernel directly, where request_firmware() will find
/drivers/firmware/
DKconfig120 This option enables the kernel to find the region of memory
/drivers/scsi/aic7xxx_old/
Daic7xxx.seq935 * that the reconnection is for - find the correct SCB and switch to it,
936 * clearing the "disconnected" bit so we don't "find" it by accident later.
963 * If we get one, we use the tag returned to find the proper
1208 * We didn't find it. Pull an SCB and DMA down the one we want.
/drivers/platform/x86/
DKconfig214 for normal use. Read the driver source to find out what it does.
/drivers/video/matrox/
Dmatroxfb_DAC1064.c965 find 1014/22 (IBM/82351); /* if found and bridging Matrox, do some strange stuff */ in MGAG100_reset()
/drivers/block/
DKconfig283 especially about where to find the server code, which runs in user
/drivers/net/wan/
DKconfig483 You can find more information and last versions of drivers and
/drivers/hwmon/
DKconfig18 To find out which specific driver(s) you need, use the
/drivers/char/
DChangeLog405 status bit change, and to find out how many changes have

12