Home
last modified time | relevance | path

Searched refs:XA (Results 1 – 6 of 6) sorted by relevance

/Linux-v5.10/arch/powerpc/math-emu/
Dmath_efp.c94 #define XA 3 macro
116 case EFSABS: ret = XA; break; in insn_type()
130 case EFSNABS: ret = XA; break; in insn_type()
131 case EFSNEG: ret = XA; break; in insn_type()
135 case EVFSABS: ret = XA; break; in insn_type()
148 case EVFSNABS: ret = XA; break; in insn_type()
149 case EVFSNEG: ret = XA; break; in insn_type()
152 case EFDABS: ret = XA; break; in insn_type()
168 case EFDNABS: ret = XA; break; in insn_type()
169 case EFDNEG: ret = XA; break; in insn_type()
[all …]
Dmath.c157 #define XA 8 macro
371 case XA: in do_mathemu()
/Linux-v5.10/Documentation/cdrom/
Dcdrom-standard.rst937 absolutely no CD-I, XA, or data tracks on it, it will be reported
942 has any XA tracks on it, it will be reported as *CDS_XA_2_1*.
952 CDS_XA_2_1 /* mixed data (XA), mode 2, form 1 (2048 user bytes) */
953 CDS_XA_2_2 /* mixed data (XA), mode 2, form 1 (2324 user bytes) */
/Linux-v5.10/Documentation/userspace-api/ioctl/
Dcdrom.rst944 If it has any XA tracks, I will return it as that. Now I
/Linux-v5.10/arch/arm/mm/
DKconfig109 Excalibur XA device family and the ARM Integrator.
/Linux-v5.10/Documentation/RCU/
DRTFP.txt24 of "quiescent states" in the VM/XA hypervisor that are guaranteed not
878 Described the relationship of the VM/XA passive serialization to RCU.