Searched full:extraction (Results 1 – 13 of 13) sorted by relevance
| /Documentation/devicetree/bindings/net/ |
| D | mscc,vsc7514-switch.yaml | 19 packet extraction/injection.
109 - description: register based extraction
110 - description: frame dma based extraction
|
| D | microchip,lan966x-switch.yaml | 38 - description: register based extraction
39 - description: frame dma based extraction
|
| D | microchip,sparx5-switch.yaml | 54 - description: register based extraction
55 - description: frame dma based extraction
|
| /Documentation/networking/device_drivers/ethernet/freescale/ |
| D | gianfar.rst | 27 extraction of VLAN headers, but not filtering. Filtering will be
|
| /Documentation/driver-api/media/drivers/ |
| D | pvrusb2.rst | 97 of the process for implementing manual firmware extraction (see
|
| D | dvb-usb.rst | 194 - firmware-extraction-2.422-problem solved, driver is now working
|
| /Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.rst | 114 The kernel's cpio extraction code is not only extremely small, it's also
|
| /Documentation/process/ |
| D | maintainer-tip.rst | 402 they just complicate automated extraction of tags.
|
| /Documentation/bpf/ |
| D | btf.rst | 436 The latter is for future extraction of map key/value type id's from a
|
| /Documentation/admin-guide/ |
| D | quickly-build-trimmed-linux.rst | 573 during extraction. The rest of the step-by-step guide will work just fine, apart
|
| D | devices.txt | 2598 0 = /dev/tnf/t0 Trace 0 data extraction
2599 1 = /dev/tnf/t1 Trace 1 data extraction
|
| D | kernel-parameters.txt | 5896 retain_initrd [RAM] Keep initrd memory after extraction. After boot, it will
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 21 …the following data query operations: search, extraction, compression, decompression, and translati…
|