Home
last modified time | relevance | path

Searched refs:x32 (Results 1 – 25 of 82) sorted by relevance

1234

/Linux-v5.4/arch/x86/entry/syscalls/
Dsyscall_64.tbl9 # The abi is "common", "64" or "x32" for this file.
362 # x32-specific system call numbers start at 512 to avoid cache impact
367 512 x32 rt_sigaction __x32_compat_sys_rt_sigaction
368 513 x32 rt_sigreturn sys32_x32_rt_sigreturn
369 514 x32 ioctl __x32_compat_sys_ioctl
370 515 x32 readv __x32_compat_sys_readv
371 516 x32 writev __x32_compat_sys_writev
372 517 x32 recvfrom __x32_compat_sys_recvfrom
373 518 x32 sendmsg __x32_compat_sys_sendmsg
374 519 x32 recvmsg __x32_compat_sys_recvmsg
[all …]
DMakefile35 syshdr_abi_unistd_x32 := common,x32
44 syshdr_abi_unistd_64_x32 := x32
/Linux-v5.4/tools/perf/arch/x86/entry/syscalls/
Dsyscall_64.tbl9 # The abi is "common", "64" or "x32" for this file.
362 # x32-specific system call numbers start at 512 to avoid cache impact
367 512 x32 rt_sigaction __x32_compat_sys_rt_sigaction
368 513 x32 rt_sigreturn sys32_x32_rt_sigreturn
369 514 x32 ioctl __x32_compat_sys_ioctl
370 515 x32 readv __x32_compat_sys_readv
371 516 x32 writev __x32_compat_sys_writev
372 517 x32 recvfrom __x32_compat_sys_recvfrom
373 518 x32 sendmsg __x32_compat_sys_sendmsg
374 519 x32 recvmsg __x32_compat_sys_recvmsg
[all …]
/Linux-v5.4/drivers/scsi/aic7xxx/
Daic79xx_seq.h_shipped20 0x00, 0x32, 0x21, 0x60,
32 0x02, 0x30, 0x51, 0x32,
80 0x01, 0x0b, 0xae, 0x32,
86 0x02, 0x8c, 0x59, 0x32,
97 0x04, 0x7c, 0x88, 0x32,
99 0x04, 0x40, 0x89, 0x32,
126 0x04, 0xac, 0x49, 0x32,
142 0x02, 0xa0, 0xc0, 0x32,
149 0x02, 0xa0, 0x40, 0x32,
155 0x02, 0x28, 0x55, 0x32,
[all …]
Daic7xxx_seq.h_shipped65 0x01, 0x3d, 0x32, 0x31,
70 0x01, 0x66, 0x32, 0x31,
81 0x01, 0x66, 0x32, 0x31,
85 0x01, 0x66, 0x32, 0x31,
89 0xff, 0x6a, 0x32, 0x01,
195 0x01, 0x64, 0x32, 0x31,
205 0x01, 0x06, 0x32, 0x31,
229 0x01, 0x69, 0x32, 0x31,
245 0xe0, 0x64, 0x32, 0x74,
419 0x08, 0xeb, 0x32, 0x6b,
[all …]
/Linux-v5.4/Documentation/media/uapi/v4l/
Dpixfmt-nv12mt.rst19 memory layout. Pixels are grouped in macroblocks of 64x32 size. The
27 grouped into 64x32 macroblocks. The three components are separated into
29 are grouped into 64x32 macroblocks. The CbCr plane has the same width,
31 The chroma plane is also grouped into 64x32 macroblocks.
/Linux-v5.4/arch/arm64/boot/dts/broadcom/stingray/
Dstingray-clock.dtsi52 reg = <0x0001d104 0x32>,
64 reg = <0x0001d1ac 0x32>,
76 reg = <0x0001d1e0 0x32>,
86 reg = <0x0001d214 0x32>,
98 reg = <0x0001d248 0x32>,
/Linux-v5.4/net/wireless/certs/
Dsforshee.hex11 0x18, 0x0f, 0x32, 0x31, 0x31, 0x37, 0x30, 0x39,
12 0x31, 0x32, 0x31, 0x39, 0x34, 0x30, 0x33, 0x35,
26 0x5b, 0xd4, 0x97, 0x32, 0x3d, 0x71, 0x8b, 0x3b,
43 0x32, 0x77, 0x07, 0x29, 0x12, 0x66, 0x1e, 0x36,
64 0x6a, 0x28, 0xf2, 0x34, 0x5c, 0x23, 0x3f, 0x32,
/Linux-v5.4/arch/x86/entry/vdso/
DMakefile34 vdso_img-$(VDSOX32-y) += x32
111 vobjx32s-y := $(vobjs-y:.o=-x32.o)
120 $(obj)/%-x32.o: $(obj)/%.o FORCE
121 $(call if_changed,x32)
/Linux-v5.4/Documentation/devicetree/bindings/clock/st/
Dst,flexgen.txt22 | |->| | | | | | x32 | | x32 | | |
/Linux-v5.4/Documentation/devicetree/bindings/leds/
Dleds-lp55xx.txt39 reg = <0x32>;
74 reg = <0x32>;
171 reg = <0x32>;
/Linux-v5.4/drivers/net/wan/
Dwanxlfw.inc_shipped121 0x00,0x00,0x32,0x10,0x02,0x81,0x00,0x00,0x00,0xE7,0x0C,0x41,0x00,0x42,0x66,0x00,
122 0x00,0x0A,0x32,0x3C,0x0E,0x08,0x60,0x00,0x00,0x3E,0x0C,0x41,0x00,0x63,0x66,0x00,
123 0x00,0x0A,0x32,0x3C,0x04,0x08,0x60,0x00,0x00,0x2E,0x0C,0x41,0x00,0x84,0x66,0x00,
124 0x00,0x0A,0x32,0x3C,0x02,0x08,0x60,0x00,0x00,0x1E,0x0C,0x41,0x00,0xA5,0x66,0x00,
125 0x00,0x0A,0x32,0x3C,0x0D,0x08,0x60,0x00,0x00,0x0E,0x32,0x3C,0x00,0x08,0x34,0x3C,
128 0x67,0x00,0x00,0x0C,0x31,0x81,0x09,0xB0,0x00,0x00,0x19,0xAC,0x30,0x81,0x32,0x39,
130 0x32,0x10,0x02,0x41,0xFF,0xF7,0x60,0x00,0x00,0x08,0x32,0x10,0x00,0x41,0x00,0x08,
148 0x6F,0x70,0x79,0x72,0x69,0x67,0x68,0x74,0x20,0x28,0x43,0x29,0x20,0x32,0x30,0x30,
/Linux-v5.4/tools/build/
DMakefile.feature82 compile-x32 \
161 $(call feature_check,compile-x32)
/Linux-v5.4/Documentation/devicetree/bindings/rtc/
Depson,rx8900.txt19 reg = <0x32>;
Depson,rx6110.txt18 reg = <0x32>;
/Linux-v5.4/arch/arm64/boot/dts/broadcom/northstar2/
Dns2-clock.dtsi71 reg = <0x6501d098 0x32>,
99 reg = <0x6501d0c4 0x32>,
/Linux-v5.4/Documentation/devicetree/bindings/power/supply/
Dmicrochip,ucs1002.txt22 reg = <0x32>;
/Linux-v5.4/arch/arm/boot/dts/
Dmeson8-minix-neo-x8.dts50 reg = <0x32>;
Dzynq-zturn.dts55 gpios = <&gpio0 0x32 0x1>;
/Linux-v5.4/Documentation/trace/
Dkprobetrace.rst59 (x8/x16/x32/x64), "string", "ustring" and bitfield
72 in decimal ('s' and 'u') or hexadecimal ('x'). Without type casting, 'x32'
73 or 'x64' is used depends on the architecture (e.g. x86-32 uses x32, and
86 types, <base-type>[1] is equal to <base-type> (e.g. +0(%di):x32[1] is same
87 as +0(%di):x32.) But string[1] is not equal to string. The string type itself
Duprobetracer.rst52 (x8/x16/x32/x64), "string" and bitfield are supported.
64 in decimal ('s' and 'u') or hexadecimal ('x'). Without type casting, 'x32'
65 or 'x64' is used depends on the architecture (e.g. x86-32 uses x32, and
/Linux-v5.4/Documentation/process/
Dadding-syscalls.rst186 x86 (including all of x86_64, x86_32 and x32).
256 way (see below), this involves a "common" entry (for x86_64 and x32) in
368 Second, you need to figure out what should happen for the x32 ABI version of
372 If there's a pointer-to-a-pointer involved, the decision is easy: x32 is
374 ``arch/x86/entry/syscalls/syscall_64.tbl`` is split so that x32 programs hit
379 555 x32 xyzzy __x32_compat_sys_xyzzy
382 call for the x32 ABI (and consequently the entry in
386 layout do indeed map exactly from x32 (-mx32) to either the 32-bit (-m32) or
426 of the system call rather than the native 64-bit version. Also, if the x32 ABI
472 and x32 (-mx32) ABI program.
[all …]
/Linux-v5.4/arch/s390/crypto/
Dcrc32be-vx.S64 .quad 0x0f200aa66, 1 << 32 # R5, x32
/Linux-v5.4/Documentation/devicetree/bindings/mfd/
Drn5t618.txt34 reg = <0x32>;
/Linux-v5.4/Documentation/translations/it_IT/process/
Dadding-syscalls.rst206 solitamente x86 (ovvero tutti: x86_64, x86_32 e x32).
287 dovete aggiungere un elemento *common* (per x86_64 e x32) in
414 per la versione dell'ABI x32. Qui C'è una scelta da fare: gli argomenti
417 Se c'è un puntatore ad un puntatore, la decisione è semplice: x32 è ILP32,
420 x32 eseguano la chiamata *compatibile*::
424 555 x32 xyzzy __x32_compat_sys_xyzzy
427 sistema a 64-bit per l'ABI x32 (e di conseguenza la voce in
431 abbiano un'esatta corrispondenza da x32 (-mx32) al loro equivalente a
479 se l'implementazione dell'ABI x32 è diversa da quella x86_64, allora la sua
530 funzioni quando viene compilato per x86_64 (-m64), x86_32 (-m32) e x32 (-mx32).
[all …]

1234