Forum: Official UlaunchELF Forums - Discussion for the most unofficial build of launchELF!


The above video goes away if you are a member and logged in, so log in now!




 
Would you like to get all the new info from
PSX-Scene in your email each day?




Want to learn more about the team keeping you up to date with the latest scene news?

Read about them now!

Check out our Developer bios, too!

 


User Tag List

Thread: Reset IOP
  

Results 1 to 2 of 2
  1. #1 Question Reset IOP 
    cyx
    cyx is offline Member
    Join Date
    Jan 2004
    Posts
    190
    Downloads
    3
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    anyone care to explain what is "reset IOP" for ? and case where it should on/off.
    Reply With Quote  

  2. #2  
    dlanor is offline Member
    Join Date
    Sep 2004
    Location
    Sweden
    Posts
    10,107
    Downloads
    5
    Uploads
    0
    Mentioned
    1 Post(s)
    Tagged
    2 Thread(s)
    Likes Given
    0
    Likes Received
    126
    Quote Originally Posted by cyx
    anyone care to explain what is "reset IOP" for ? and case where it should on/off.
    OK, here're the basics about it.

    The PS2 has two main processors that work in parallel. The 'chief' is known as the EE (idiotic Sony abbreviation for "Emotion Engine", believe it or not... ), which runs the main code of most programs, be they games or LaunchELF etc.

    The secondary processor is known as IOP, a somewhat better abbreviation of "Input Output Processor". Each of these processors has separate RAM, or as we often say, they live in separate spaces, EE space and IOP space. They can 'peek' into the other space, and even 'poke' a little, but the main communication between them is through an RPC protocol (Remote Procedure Call), and a series of Sifxxx functions. (System InterFace)

    When a program in EE space needs to access hardware of various kinds, it needs device drivers for that, So it uses some of the function calls mentioned above to load IRX drivers into IOP space, and then the RPC functions can be used to access functions of those drivers, almost as if they were running on the same processor as the calling program.

    However, when one EE program is launched by another such program, it is possible that the needs of the new program conflicts with those of the old one, so that it becomes necessary to throw out the IRXs already loaded, and make a fresh start. That is the purpose of IOP reset.

    For most cases where you use LaunchELF, you should have IOP reset active, as it eliminates the risk of using incompatible drivers, possibly left in IOP RAM by whatever program launched LaunchELF. But in some cases you need to disable IOP reset, precisely because you want to keep old IRXs active. One typical example of that would be when you use PS2Link to run LaunchELF, and want to retain the ability to reset PS2Link by network commands sent from the PC.

    Best regards: dlanor
    Reply With Quote  

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •