Lines Matching refs:the

10 To the maximum extent permitted by applicable law,
13 and any warranty against infringement with regard to the SOFTWARE
16 To the maximum extent permitted by applicable law,
21 Motorola assumes no responsibility for the maintenance and support of the SOFTWARE.
23 You are hereby granted a copyright license to use, modify, and distribute the SOFTWARE
32 The file isp.sa contains the 68060 Integer Software Package.
34 integrated into an operating system to handle the "Unimplemented
36 This exception is taken when any of the integer instructions
37 not hardware implemented on the 68060 are encountered. The
51 The file isp.sa is essentially a hexadecimal image of the
52 release package. This is the ONLY format which will be supported.
53 The hex image was created by assembling the source code and
54 then converting the resulting binary output image into an
56 using the Motorola Assembly Syntax assembler directive "dc.l"
62 the installer should add a symbolic label to the top of the file.
63 This will allow calling routines to access the entry points
88 The first section of this module is the "Call-out" section. This section
90 the end of the file iskeleton.s). The purpose of this section is to allow
91 the ISP routines to reference external functions that must be provided
92 by the host operating system. This section MUST be exactly 128 bytes in
94 to a function required by the ISP (these functions and their location are
96 the address of the corresponding function RELATIVE to the starting address
97 of the "call-out" section. The "Call-out" section must sit adjacent to the
100 The second section, the "Entry-point" section, is used by external routines
101 to access the functions within the ISP. Since the isp.sa hex file contains
103 with respect to the top of the package. The currently defined entry-points
105 would simply execute a "bra" or "jmp" that jumped to the selected function
108 For example, if the 68060 hardware took a "Unimplemented Integer Instruction"
109 exception (vector #61), the operating system should execute something
114 (_060ISP_TOP is the starting address of the "Call-out" section; the "Call-out"
115 section is 128 bytes long; and the Unimplemented Integer ISP handler entry
116 point is located 0 bytes from the top of the "Entry-point" section.)
118 The third section is the code section. After entering through an "Entry-point",
119 the entry code jumps to the appropriate emulation code within the code section.
175 address) take the Unimplemented Integer Instruction exception. When the
176 060ISP is installed properly, these instructions will enter through the
177 _060_isp_unimp() entry point of the ISP.
179 After the 060ISP decodes the instruction type and fetches the appropriate
180 data registers, and BEFORE the actual emulated transfers occur, the
181 package calls either the "Call-out" _060_real_cas() or _060_real_cas2().
182 If the emulation code provided by the 060ISP is sufficient for the
184 made, by the system integrator, to point directly back into the package
185 through the "Entry-point"s _060_isp_cas() or _060_isp_cas2().
187 One other necessary action by the integrator is to supply the routines
189 defined further in iskeleton.s and the 68060 Software Package Specification.
191 If the "core" emulation routines of either "cas" or "cas2" perform some
192 actions which are too system-specific, then the system integrator must
194 the functions _060_real_cas() or _060_real_cas2(). When this new emulation
195 code has completed, then it should re-enter the 060ISP package through the
197 To see what the register state is upon entering _060_real_cas() or
198 _060_real_cas2() and what it should be upon return to the package through
199 _060_isp_cas_finish() or _060_isp_cas2_finish(), please refer to the