Home
last modified time | relevance | path

Searched full:060 (Results 1 – 25 of 57) sorted by relevance

123

/openbmc/linux/arch/m68k/ifpsp060/
H A Dfskeleton.S59 | Software Package. For a normal exit, all 060FPSP routines call this
70 | This is the exit point for the 060FPSP when an enabled overflow exception
89 | This is the exit point for the 060FPSP when an enabled underflow exception
107 | This is the exit point for the 060FPSP when an enabled operand error exception
126 | This is the exit point for the 060FPSP when an enabled signalling NaN exception
145 | This is the exit point for the 060FPSP when an enabled divide-by-zero exception
164 | This is the exit point for the 060FPSP when an enabled inexact exception
183 | This is the exit point for the 060FPSP when an enabled bsun exception
205 | This is the exit point for the 060FPSP when an F-Line Illegal exception is
208 | the FPU is disabled, and F-Line Illegal instructions. The 060FPSP module
[all …]
H A Dfpsp.doc169 - documented in 3.5 of 060SP spec.
177 - documented in 3.5 of 060SP spec.
185 - documented in 3.7 of 060SP spec.
193 - documented in 3.6 of 060SP spec.
202 - documented in 3.4 of 060SP spec.
214 - documented in 3.4 of 060SP spec.
227 - not fully documented in 060SP spec.
264 - documented in 3.1 of 060SP spec.
286 - documented in 3.3 of 060 spec.
H A Disp.doc176 060ISP is installed properly, these instructions will enter through the
179 After the 060ISP decodes the instruction type and fetches the appropriate
182 If the emulation code provided by the 060ISP is sufficient for the
195 code has completed, then it should re-enter the 060ISP package through the
H A Dos.S61 | When installing the 060SP, the _copyin()/_copyout() equivalents for a
64 | The addresses within the 060SP are guaranteed to be on the stack.
353 | This is the exit point for the 060FPSP when an instruction is being traced
366 | This is the exit point for the 060FPSP when an access error exception
H A DCHANGES97 stated that ONLY "bit 0" would be set. The 060SP attempts to set a few
119 stated that ONLY "bit 0" would be set. The 060SP attempts to set a few
H A Diskeleton.S189 | SO THAT THE 060SP CAN CREATE A PROPER ACCESS ERROR FRAME.
346 | 060 INTEGER KERNEL PACKAGE MUST GO HERE!!!
H A Dilsp.doc80 the 060ILSP entry table. A compiler generated code sequence
H A DTEST.DOC95 For example, to run the 060ISP test, write a program that includes the
/openbmc/openbmc/meta-arm/meta-arm-bsp/wic/
H A Dcorstone1000-flash-firmware.wks.in22 …imary" --uuid 07F9616C-1233-439C-ACBA-72D75421BF70 --part-type D763C27F-07F6-4FF0-B2F3-060CB465CD4E
33 …ndary" --uuid 009A6A12-64A6-4F0F-9882-57CD79A34A3D --part-type D763C27F-07F6-4FF0-B2F3-060CB465CD4E
/openbmc/linux/arch/m68k/mm/
H A Dmemory.c84 /* ... but on the '060, CPUSH doesn't invalidate (for us, since we have set
156 * the '060! in cache_push()
H A Dkmap.c27 * For 040/060 we can use the virtual memory area like other architectures,
/openbmc/linux/arch/m68k/include/uapi/asm/
H A Dbootinfo-atari.h34 #define ATARI_MACH_HADES 2 /* Hades 040 or 060 */
/openbmc/openbmc/poky/meta/recipes-devtools/rpm/files/
H A D0001-Do-not-reset-the-PATH-environment-variable-before-ru.patch16 index 060fd8124..4dc6466a8 100644
H A D0001-When-cross-installing-execute-package-scriptlets-wit.patch32 index 097c9055a..060fd8124 100644
/openbmc/linux/drivers/zorro/
H A Dzorro.ids129 1700 WildFire 060 [Accelerator]
130 ff00 WildFire 060 [Accelerator]
153 1600 GForce 040/060 [Accelerator and SCSI Host Adapter]
/openbmc/linux/arch/m68k/include/asm/
H A Dmath-emu.h166 * 020/030 use a different stack frame then 040/060, for the
167 * 040/060 the return pc points already to the next location,
/openbmc/linux/Documentation/arch/x86/
H A Dzero-page.rst20 060/010 ALL ist_info Intel SpeedStep (IST) BIOS support information
/openbmc/linux/arch/m68k/kernel/
H A Dentry.S371 /* The 060 FPU keeps status in bits 15-8 of the first longword */
403 /* The 060 FPU keeps status in bits 15-8 of the first longword */
H A Dvectors.c48 * use some instruction that are emulated on the 060
H A Dhead.S207 * and any of the models (030, 040, 060, etc.).
307 CPUTYPE_060 = 2 /* indicates an 060 */
674 * Test the BootInfo cputype for 060
726 * '040 or '060
1278 * '060. But analysis of the reasons for this, and practical
1571 * one of two things. On 040/060 class machines, it points to
2009 * On 030, 040 & 060 it will attempt to use Transparent Translation
2157 * MMU 040 & 060 Support
2159 * The MMU usage for the 040 and 060 is different enough from
/openbmc/linux/arch/ia64/kernel/
H A Desi.c30 #define ESI_DESC_SIZE(type) "\060"[(unsigned) (type)]
/openbmc/linux/drivers/scsi/
H A Dzorro7xx.c46 { .name = "GForce 040/060", .offset = 0x40000 },
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/
H A D0012-Platform-CS1000-Increase-BL2-partition-size.patch57 TFM_TYPE_UUID="D763C27F-07F6-4FF0-B2F3-060CB465CD4E"
/openbmc/linux/arch/powerpc/boot/
H A Drs6000.h158 #define N_TMASK (060)
/openbmc/linux/arch/m68k/
H A DKconfig.cpu417 config 060_WRITETHROUGH

123