Searched refs:compatibility (Results 1 – 19 of 19) sorted by relevance
6 | Copy the PC to FPIAR to maintain 881/882 compatibility
16 | destination is not affected. For 68881 compatibility, the
7 | For 881/2 compatibility, sw must denormalize the intermediate
57 * The ASSERT() sink to . is intentional, for binutils 2.14 compatibility:
113 * At this point we're in long mode but in 32bit compatibility mode
112 unsigned long compatibility; member
209 compatibility with 32bit applications, a page size of 4KB should be213 4KB For best 32bit compatibility
250 invalid arguments. It is provided only for backwards compatibility.263 invalid arguments. It is provided only for backwards compatibility.
267 IA-32 compatibility, a page size of 4KB should be selected (the vast272 4KB For best IA-32 compatibility
504 /* Needed for dtbImage boot wrapper compatibility */
538 in compatibility mode, supports setting a variable number of bits for610 compatibility...
290 reg = <0x20000 0x4000>; /* for compatibility with older PAMU drivers */
245 reg = <0x20000 0x5000>; /* for compatibility with older PAMU drivers */
258 reg = <0x20000 0x4000>; /* for compatibility with older PAMU drivers */
285 reg = <0x20000 0x4000>; /* for compatibility with older PAMU drivers */
293 reg = <0x20000 0x5000>; /* for compatibility with older PAMU drivers */
147 bus while maintaining backward compatibility with cards made for1643 disambiguate both ABIs and allow for backward compatibility support1653 new (ARM EABI) one. It also provides a compatibility layer to1953 This is meant as a backward compatibility convenience for those
2728 bus while maintaining backward compatibility with cards made for
2277 bus while maintaining backward compatibility with cards made for