Home
last modified time | relevance | path

Searched refs:x64 (Results 1 – 25 of 142) sorted by relevance

123456

/linux/drivers/scsi/aic7xxx/
H A Daic7xxx_seq.h_shipped194 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/arch/x86/include/asm/
H A Dsyscall_wrapper.h108 __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/arch/arm64/boot/dts/marvell/mmp/
H A Dpxa1908.dtsi132 reg = <0x10800 0x64>;
143 reg = <0x11000 0x64>;
154 reg = <0x13800 0x64>;
271 reg = <0x37000 0x64>;
/linux/Documentation/firmware-guide/acpi/
H A Dvideo_extension.rst50 0x64,
61 0x64
69 0x64 brightness value) inclusive. Each of those index values is regarded
/linux/drivers/tty/vt/
H A Ducs_fallback_table.h_shipped121 { 0xF0, 0x64 }, /* LATIN SMALL LETTER ETH -> 'd' */
147 { 0x0F, 0x64 }, /* LATIN SMALL LETTER D WITH CARON -> 'd' */
149 { 0x11, 0x64 }, /* LATIN SMALL LETTER D WITH STROKE -> 'd' */
227 { 0x64, 0x54 }, /* LATIN CAPITAL LETTER T WITH CARON -> 'T' */
266 { 0x8C, 0x64 }, /* LATIN SMALL LETTER D WITH TOPBAR -> 'd' */
267 { 0x8D, 0x64 }, /* LATIN SMALL LETTER TURNED DELTA -> 'd' */
384 { 0x21, 0x64 }, /* LATIN SMALL LETTER D WITH CURL -> 'd' */
430 { 0x56, 0x64 }, /* LATIN SMALL LETTER D WITH TAIL -> 'd' */
431 { 0x57, 0x64 }, /* LATIN SMALL LETTER D WITH HOOK -> 'd' */
440 { 0x64, 0x75 }, /* LATIN SMALL LETTER RAMS HORN -> 'u' */
[all …]
/linux/drivers/media/platform/imagination/
H A DKconfig13 semiplanar video formats, with resolution ranging from 64x64 to 8K x 8K
/linux/lib/crypto/
H A Dcurve25519-fiat32.c138 { 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/drivers/of/unittest-data/
H A Dtests-platform.dtsi48 test,ref-arg = <&ref_child_0 0x10 0x64>;
/linux/arch/mips/boot/dts/loongson/
H A Dloongson64g-package.dtsi26 reg = <0 0x3ff01400 0x64>;
H A Dloongson64c-package.dtsi29 reg = <0 0x3ff01400 0x64>;
H A Dloongson64v_4core_virtio.dts28 reg = <0 0x3ff01400 0x64>;
/linux/Documentation/devicetree/bindings/phy/
H A Dti-phy.txt74 <0x4a084800 0x64>,
90 <0x4A096400 0x64>, /* phy_tx */
/linux/Documentation/i2c/
H A Dslave-eeprom-backend.rst16 24c02, read/write, address 0x64:
/linux/drivers/gpu/drm/ci/xfails/
H A Drockchip-rk3288-flakes.txt20 kms_cursor_edge_walk@64x64-left-edge
/linux/Documentation/trace/
H A Duprobetracer.rst54 (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/Documentation/devicetree/bindings/leds/
H A Dleds-lm3601x.txt37 reg = <0x64>;
/linux/net/wireless/certs/
H A Dwens.hex25 0xb3, 0x90, 0x86, 0xda, 0xd3, 0x64, 0x81, 0x1f,
69 0xdb, 0x76, 0x64, 0x42, 0x70, 0xc9, 0xc0, 0xeb,
/linux/Documentation/usb/
H A Dlinux.inf23 ; Decoration for x64 architecture
/linux/arch/arm/boot/dts/nxp/imx/
H A Dimx27-phytec-phycard-s-rdk.dts63 reg = <0x64>;
H A Dimx6qdl-phytec-pbab01.dtsi134 reg = <0x64>;
/linux/arch/arm/boot/dts/intel/socfpga/
H A Dsocfpga_cyclone5_mercury_sa2.dtsi58 reg = <0x64>;
H A Dsocfpga.dtsi318 div-reg = <0x64 0 2>;
326 div-reg = <0x64 2 2>;
333 div-reg = <0x64 4 3>;
341 div-reg = <0x64 7 3>;
/linux/Documentation/bpf/
H A Dbpf_design_QA.rst18 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/Documentation/translations/zh_CN/arch/arm64/
H A Dbooting.txt101 u32 magic = 0x644d5241; /* 魔数, 小端, "ARM\x64" */
/linux/arch/arm/boot/dts/st/
H A Dspear320.dtsi135 st-plgpio,ie-reg = <0x64>;

123456