Home
last modified time | relevance | path

Searched refs:classic (Results 1 – 25 of 71) sorted by relevance

123

/linux-6.1.9/arch/arm/boot/dts/
Dsun8i-r16-nintendo-super-nes-classic.dts5 #include "sun8i-r16-nintendo-nes-classic.dts"
9 compatible = "nintendo,super-nes-classic", "nintendo,nes-classic",
Dnspire-classic.dtsi3 * linux/arch/arm/boot/nspire-classic.dts
47 compatible = "lsi,nspire-classic-clock";
51 compatible = "lsi,nspire-classic-ahb-divider";
78 compatible = "ti,nspire-classic-lcd-panel";
Dnspire-clp.dts9 /include/ "nspire-classic.dtsi"
Dnspire-tp.dts9 /include/ "nspire-classic.dtsi"
Dsun8i-r16-nintendo-nes-classic.dts10 compatible = "nintendo,nes-classic", "allwinner,sun8i-r16",
/linux-6.1.9/sound/isa/msnd/
DMakefile5 snd-msnd-classic-objs := msnd_classic.o
9 obj-$(CONFIG_SND_MSND_CLASSIC) += snd-msnd-classic.o snd-msnd-lib.o
/linux-6.1.9/Documentation/networking/
Dnf_flowtable.rst22 classic IP forwarding path (the visible effect is that you do not see these
25 follows the classic IP forwarding path.
34 classic IP forwarding path unless the user explicitly instruct flows to use this
37 The flowtable datapath is represented in Fig.1, which describes the classic IP
73 mangled according to the NAT policy that is specified from the classic IP
75 traffic is passed up to follow the classic IP forwarding path given that the
77 TCP RST and FIN packets are also passed up to the classic IP forwarding path to
79 the classic forwarding path to report packet-too-big ICMP errors to the sender.
158 such as PVID and untagged. You can also stack a classic VLAN device on top of
/linux-6.1.9/Documentation/devicetree/bindings/clock/
Dnspire-clock.txt6 "lsi,nspire-classic-ahb-divider" for the AHB divider in the older model
8 "lsi,nspire-classic-clock" for the base clock in the older model
/linux-6.1.9/Documentation/bpf/
Dclassic_vs_extended.rst10 Some core changes of the eBPF format from classic BPF:
243 eBPF is reusing most of the opcode encoding from classic to simplify conversion
244 of classic BPF to eBPF.
277 * in classic BPF, this means::
323 So BPF_ADD | BPF_X | BPF_ALU means 32-bit addition in both classic BPF
324 and eBPF. There are only two registers in classic BPF, so it means A += X.
326 BPF_XOR | BPF_K | BPF_ALU means A ^= imm32 in classic BPF and analogous
370 BPF_IMM 0x00 /* used for 32-bit mov in classic BPF and 64-bit in eBPF */
374 BPF_LEN 0x80 /* classic BPF only, reserved in eBPF */
375 BPF_MSH 0xa0 /* classic BPF only, reserved in eBPF */
Dbpf_licensing.rst13 instruction set is now known as "classic BPF".
22 In 2014, the classic BPF instruction set was significantly extended. We
Dlinux-notes.rst20 carried over from classic BPF to retain the performance of legacy socket
/linux-6.1.9/Documentation/ABI/testing/
Dsysfs-driver-hid-wiimote17 extensions. It can be one of: none, motionp, nunchuck, classic,
18 motionp+nunchuck, motionp+classic
20 the official Nintendo Nunchuck extension and classic is the
/linux-6.1.9/tools/memory-model/litmus-tests/
DR+poonceonces.litmus7 * classic counterintuitive litmus tests that illustrates the effects of
DR+fencembonceonces.litmus6 * This is the fully ordered (via smp_mb()) version of one of the classic
/linux-6.1.9/Documentation/devicetree/bindings/display/panel/
Dti,nspire.yaml19 - ti,nspire-classic-lcd-panel
/linux-6.1.9/net/can/
DKconfig64 (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
69 ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
/linux-6.1.9/Documentation/core-api/irq/
Dconcepts.rst23 of the hardware involved. The ISA IRQs are a classic example of
/linux-6.1.9/Documentation/admin-guide/LSM/
DYama.rst51 0 - classic ptrace permissions:
62 classic criteria is also met. To change the relationship, an
/linux-6.1.9/Documentation/translations/zh_CN/mm/
Dmemory-model.rst88 通过SPARSEMEM,有两种可能的方式将PFN转换为相应的 `struct page` --"classic sparse"和
/linux-6.1.9/Documentation/kbuild/
Dkconfig.rst228 - classic => theme with blue background. The classic look
229 - bluetitle => a LCD friendly version of classic. (default)
/linux-6.1.9/Documentation/arm/sa1100/
Dserial_uart.rst43 name. The classic example is the content of the /etc/inittab file where
/linux-6.1.9/Documentation/userspace-api/media/v4l/
Dio.rst13 The classic I/O method using the :c:func:`read()` and
/linux-6.1.9/Documentation/x86/
Dusb-legacy-support.rst13 their classic PS/2 counterparts. This means one can use an USB keyboard to
/linux-6.1.9/Documentation/arm/stm32/
Dstm32-dma-mdma-chaining.rst174 the one you should already have for "classic" DMA operation.
307 the memory address must point to the buffer originally used for "classic"
336 In the same way you get your descriptor for your "classic" DMA operation,
396 DMA_DEV_TO_MEM and keep the "classic" DMA usage for DMA_MEM_TO_DEV, unless
/linux-6.1.9/kernel/bpf/
DKconfig3 # BPF interpreter that, for example, classic socket filters depend on.

123