Searched full:looks (Results 1 – 25 of 996) sorted by relevance
12345678910>>...40
| /Linux-v5.4/scripts/mod/ |
| D | file2alias.c | 156 /* Looks like "usb:vNpNdNdcNdscNdpNicNiscNipNinN" */
387 /* Looks like: hid:bNvNpN */
405 /* Looks like: ieee1394:venNmoNspNverN */
429 /* Looks like: pci:vNdNsvNsdNbcNscNiN. */
472 /* looks like: "ccw:tNmNdtNdmN" */
495 /* looks like: "ap:tN" */
505 /* looks like: "css:tN" */
515 /* Looks like: "serio:tyNprNidNexN" */
534 /* looks like: "acpi:ACPI0003" or "acpi:PNP0C0B" or "acpi:LNXVIDEO" or
571 /* looks like: "pnp:dD" */
[all …]
|
| /Linux-v5.4/arch/s390/kernel/ |
| D | ftrace.c | 25 * The mcount code looks like this:
32 * The enabled ftrace code block looks like this:
44 * The disabled ftrace code block looks like this:
52 * function prologue contains only a single six byte instruction and looks
55 * To enable ftrace the code gets patched like above and afterwards looks
|
| /Linux-v5.4/drivers/staging/wusbcore/Documentation/ |
| D | wusb-design-overview.rst | 105 USB. The Wireless USB Host Controller in a HWA looks to the host like a
118 *HC*: the wireless USB host controller. It looks like a USB host
120 To the system it looks like a separate USB host. The driver (will)
128 package provides a driver for it (it looks like a network
138 USB. To the system it looks like yet another USB host. To the untrained
139 eye, it looks like a hub that connects upstream wirelessly.
186 neighborhood looks, creating and destroying devices as they show up or
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | am335x-osd335x-common.dtsi | 26 * Therefore, from a DEVICE_ID revision point of view, the silicon looks
28 * the HW OPP table, the silicon looks like it is Revision 1.0 (ie the
|
| /Linux-v5.4/arch/unicore32/kernel/ |
| D | stacktrace.c | 22 * With framepointer enabled, a simple function prologue looks like this:
27 * A simple function epilogue looks like this:
|
| /Linux-v5.4/arch/arm/nwfpe/ |
| D | entry.S | 51 3) If an instruction has been emulated successfully, it looks ahead at
54 way it repeatedly looks ahead and executes floating point instructions
|
| /Linux-v5.4/arch/m68k/mac/ |
| D | oss.c | 48 /* Disable all interrupts. Unlike a VIA it looks like we */ in oss_init()
123 * It looks messy but it's rather straightforward. The switch() statement
|
| /Linux-v5.4/drivers/input/keyboard/ |
| D | ipaq-micro-keys.c | 32 KEY_ADDRESSBOOK, /* 3: Contacts (looks like Outlook) */
34 KEY_HOMEPAGE, /* 5: Start (looks like swoopy arrow) */
|
| /Linux-v5.4/arch/arm/kernel/ |
| D | stacktrace.c | 17 * With framepointer enabled, a simple function prologue looks like this:
22 * A simple function epilogue looks like this:
|
| /Linux-v5.4/tools/testing/radix-tree/ |
| D | regression1.c | 17 * 4. The reader looks at the index 0 slot, and finds that the page has 0 ref
19 * 5. The reader looks at it again, hoping that the item will either be freed
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | sysfs-driver-qla2xxx | 4 Description: qla2xxx-udev.sh currently looks for uevent CHANGE events to
|
| D | o2cb | 5 Description: Ocfs2-tools looks at 'interface-revision' for versioning
|
| /Linux-v5.4/drivers/staging/exfat/ |
| D | TODO | 4 exfat_core.c - fs_sync(sb,0) all over the place looks fishy as hell.
|
| /Linux-v5.4/arch/arm64/kernel/ |
| D | stacktrace.c | 23 * A simple function prologue looks like this:
28 * A simple function epilogue looks like this:
|
| /Linux-v5.4/arch/unicore32/ |
| D | Kconfig.debug | 10 it is not recommended because it looks ugly and doesn't cooperate
|
| /Linux-v5.4/arch/arm/mach-rpc/include/mach/ |
| D | io.h | 23 * These peripherals are found in an area of MMIO which looks very much
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | sharedsubtree.txt | 686 the new tree now looks like this:
704 the new tree now looks like this:
761 the new tree now looks like this:
775 the new tree now looks like this:
790 the new tree now looks like this:
843 A example propagation tree looks as shown in the figure below.
844 [ NOTE: Though it looks like a forest, if we consider all the shared
|
| /Linux-v5.4/drivers/base/firmware_loader/ |
| D | Kconfig | 69 looks for the firmware files listed in the EXTRA_FIRMWARE option.
122 looks for and cannot possibly be specified using the firmware_class
|
| /Linux-v5.4/tools/perf/pmu-events/arch/arm64/arm/cortex-a76-n1/ |
| D | cache.json | 21 … event counts any load or store operation or page table walk access which looks up in the L1 data …
45 …": "L2 data cache access. This event counts any transaction from L1 which looks up in the L2 cache…
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | procfs-smaps_rollup | 17 Typical output looks like this:
|
| /Linux-v5.4/arch/nios2/include/asm/ |
| D | pgtable-bits.h | 15 * which looks like this:
|
| /Linux-v5.4/drivers/staging/sm750fb/ |
| D | readme | 27 ahead of parameters,so,it looks like:
|
| /Linux-v5.4/Documentation/driver-api/firmware/ |
| D | direct-fs-lookup.rst | 6 by the kernel. The kernel looks for the firmware directly on the root
|
| /Linux-v5.4/Documentation/driver-api/iio/ |
| D | hw-consumer.rst | 22 A typical IIO HW consumer setup looks like this::
|
| /Linux-v5.4/Documentation/core-api/ |
| D | packing.rst | 129 7. If QUIRK_LSW32_IS_FIRST and QUIRK_LITTLE_ENDIAN are set, it looks like
141 are set, it looks like this:
|
12345678910>>...40
