| /linux-6.12.1/drivers/scsi/aic7xxx/ |
| D | aic7xxx_seq.h_shipped | 194 0x01, 0x64, 0xd8, 0x31,
195 0x01, 0x64, 0x32, 0x31,
196 0x5b, 0x64, 0xc8, 0x28,
197 0x30, 0x64, 0xca, 0x18,
199 0xff, 0x64, 0x8e, 0x79,
202 0x01, 0x64, 0x86, 0x61,
206 0xff, 0x64, 0xc8, 0x18,
207 0xff, 0x64, 0x80, 0x69,
241 0xbf, 0x64, 0x58, 0x7a,
242 0x80, 0x64, 0xa0, 0x73,
[all …]
|
| /linux-6.12.1/drivers/gpu/drm/ci/xfails/ |
| D | amdgpu-stoney-fails.txt | 27 kms_cursor_crc@cursor-onscreen-64x64,Fail
29 kms_cursor_crc@cursor-random-64x64,Fail
32 kms_cursor_crc@cursor-sliding-64x64,Fail
33 kms_cursor_edge_walk@64x64-left-edge,Fail
|
| D | rockchip-rk3399-fails.txt | 18 kms_cursor_crc@cursor-offscreen-64x64,Fail
22 kms_cursor_crc@cursor-onscreen-64x64,Fail
26 kms_cursor_crc@cursor-random-64x64,Fail
30 kms_cursor_crc@cursor-rapid-movement-64x64,Fail
35 kms_cursor_crc@cursor-sliding-64x64,Fail
36 kms_cursor_edge_walk@64x64-left-edge,Fail
|
| D | vkms-none-fails.txt | 31 kms_cursor_crc@cursor-rapid-movement-64x64,Fail
|
| /linux-6.12.1/arch/x86/include/asm/ |
| D | syscall_wrapper.h | 108 __SYS_STUB0(x64, sys_##name)
111 __SYS_STUBx(x64, sys##name, \
115 __COND_SYSCALL(x64, sys_##name)
172 __SYS_STUB0(x64, compat_sys_##name)
175 __SYS_STUBx(x64, compat_sys##name, \
179 __COND_SYSCALL(x64, compat_sys_##name)
|
| /linux-6.12.1/Documentation/virt/hyperv/ |
| D | overview.rst | 15 Hyper-V runs on x86/x64 and arm64 architectures, and Linux guests
23 * Implicit traps: As defined by the x86/x64 or arm64 architecture,
32 Hyper-V. On x86/x64, hypercalls use a Hyper-V specific calling
37 synthetic registers. On x86/x64 these registers appear as MSRs in
39 the normal mechanisms defined by the x86/x64 architecture. On
53 x86/x64 architecture only.
87 range of 4 Kbytes. Since the Linux guest page size on x86/x64 is
143 On x86/x64, Hyper-V supports 32-bit and 64-bit guests, and Linux
153 format on both x86/x64 and arm64. Big-endian format on arm64 is not
|
| D | clocks.rst | 22 x86/x64
24 On x86/x64, Hyper-V provides guest VMs with a synthetic system clock
73 x86/x64 doesn't support per-CPU interrupts, Direct Mode statically
|
| /linux-6.12.1/Documentation/firmware-guide/acpi/ |
| D | video_extension.rst | 50 0x64,
61 0x64
69 0x64 brightness value) inclusive. Each of those index values is regarded
|
| /linux-6.12.1/drivers/media/platform/imagination/ |
| D | Kconfig | 13 semiplanar video formats, with resolution ranging from 64x64 to 8K x 8K
|
| /linux-6.12.1/Documentation/devicetree/bindings/net/ |
| D | marvell-bt-8xxx.txt | 64 marvell,wakeup-gap-ms = /bits/ 16 <0x64>;
81 marvell,wakeup-gap-ms = /bits/ 16 <0x64>;
|
| /linux-6.12.1/lib/crypto/ |
| D | curve25519-fiat32.c | 138 { u32 x64; u8/*bool*/ x65 = addcarryx_u25(x61, x29, x62, &x64); in fe_freeze() local
154 out[3] = x64; in fe_freeze()
358 { u64 x64 = (x63 + x57); in fe_mul_impl() local
400 { u64 x106 = (x104 + x64); in fe_mul_impl()
501 { u64 x64 = (x63 + x29); in fe_sqr_impl() local
502 { u64 x65 = (x64 >> 0x1a); in fe_sqr_impl()
503 { u32 x66 = ((u32)x64 & 0x3ffffff); in fe_sqr_impl()
681 { u64 x64 = (x63 + x57); in fe_mul_121666_impl() local
723 { u64 x106 = (x104 + x64); in fe_mul_121666_impl()
|
| /linux-6.12.1/arch/mips/boot/dts/loongson/ |
| D | loongson64g-package.dtsi | 26 reg = <0 0x3ff01400 0x64>;
|
| D | loongson64c-package.dtsi | 29 reg = <0 0x3ff01400 0x64>;
|
| D | loongson64v_4core_virtio.dts | 28 reg = <0 0x3ff01400 0x64>;
|
| /linux-6.12.1/Documentation/devicetree/bindings/phy/ |
| D | ti-phy.txt | 74 <0x4a084800 0x64>,
90 <0x4A096400 0x64>, /* phy_tx */
|
| /linux-6.12.1/Documentation/i2c/ |
| D | slave-eeprom-backend.rst | 16 24c02, read/write, address 0x64:
|
| /linux-6.12.1/Documentation/trace/ |
| D | uprobetracer.rst | 54 (x8/x16/x32/x64), "string" and bitfield are supported.
67 or 'x64' is used depends on the architecture (e.g. x86-32 uses x32, and
68 x86-64 uses x64).
|
| /linux-6.12.1/arch/arm/boot/dts/intel/socfpga/ |
| D | socfpga_arria10_mercury_aa1.dtsi | 62 reg = <0x64>;
|
| /linux-6.12.1/Documentation/devicetree/bindings/leds/ |
| D | leds-lm3601x.txt | 37 reg = <0x64>;
|
| /linux-6.12.1/arch/arm/boot/dts/aspeed/ |
| D | aspeed-bmc-opp-zaius.dts | 221 reg = <0x64>;
349 reg = <0x64>;
408 reg = <0x64>;
|
| /linux-6.12.1/net/wireless/certs/ |
| D | wens.hex | 25 0xb3, 0x90, 0x86, 0xda, 0xd3, 0x64, 0x81, 0x1f,
69 0xdb, 0x76, 0x64, 0x42, 0x70, 0xc9, 0xc0, 0xeb,
|
| /linux-6.12.1/Documentation/usb/ |
| D | linux.inf | 23 ; Decoration for x64 architecture
|
| /linux-6.12.1/arch/arm/boot/dts/nxp/imx/ |
| D | imx27-phytec-phycard-s-rdk.dts | 63 reg = <0x64>;
|
| /linux-6.12.1/Documentation/bpf/ |
| D | bpf_design_QA.rst | 18 Q: Is BPF a generic instruction set similar to x64 and arm64?
34 with two most used architectures x64 and arm64 (and takes into
47 (unlike x64 ISA that allows msft, cdecl and other conventions)
137 Q: Why BPF_DIV instruction doesn't map to x64 div?
139 A: Because if we picked one-to-one relationship to x64 it would have made
|
| /linux-6.12.1/Documentation/translations/zh_CN/admin-guide/ |
| D | bug-hunting.rst | 23 [<c12ba080>] ? dump_stack+0x44/0x64
42 [<c1055654>] ? task_work_run+0x64/0x80
|