Online

There are 29 unlogged users and 0 registered users online.

You can log-in or register for a user account here.
Log-in or register a new user account | 4 Comments
Comments are statements made by the person that posted them.
They do not necessarily represent the opinions of the site editor.

Re: Codingstyle Interview with PS2 Linux Developers

(Score: 1)
by mrbrown (-) on May 22, 2002 - 11:16 AM
(User information  | Send a message http://)
<blockquote> I'd swear that mrbrown was being paid to write this stuff. Do you work for Sony or what? </blockquote> I wish :). Seriously, everything I write comes from my own research, and from a couple of candid conversations I've had with SCEA folks (inlcuding Adam). I have no ulterior motives, I just want to see the PS2DEV (and PS2/Linux) communities grow and prosper. <blockquote> Can you confirm that the Runtime Environment does not actually hold back the programmer from accessing BIOS and loading modules onto the IOP so that sound can be added to programs,etc. </blockquote>

Correct, you can still reboot the IOP and load your own modules even after the RTE has loaded. It only provides a library interface, it does nothing more to take over the system. You'd actually be surprised as to how simple it is underneath it all.

I'm currently working on a set of routines for Linux that duplicate the low-level SIF command and RPC functionality that the RTE provides. Think of it as a poor man's PS2LIB for Linux :). Once this is in and working it should be possible to boot Linux without the PS2/Linux kit at all.

The end-goal is to provide GPL device drivers for all PS2 hardware, and slowly phase out the closed portions.

<blockquote> I'm also really glad that its possible to load programs via the memory card. Could you explain why I need the ps2linux kit as a hobbiest if this method is possible? I'd really prefer a memory card boot method and if this is possible without the ps2linux kit I'd be the first to write the code to make it work. Could you please explain further this technique so that I can do it? </blockquote>

The PS2/Linux DVD bootloader is responsible for loading the ELF from memory card. It does this under the directory "BWLINUX", which is the only directory on the memcard that Linux programs have access to. When under Linux (or using another method), copy your ELF file to this directory. I think you may also have to edit a parameter file on the memcard as well, I'm not sure. Once you do this, reboot using the PS2/Linux DVD and you'll be able to load and execute your ELF.

It's not possible to automatically load an arbitrary ELF without the PS2/Linux boot disc.

As far as the rest of your comments go - don't get me wrong. I don't want to denegrate all of the hard work that has gone into the PS2DEV tools, libraries, and documentation. You're right, using Naplink and the PL2301 USB cable is a cheap way to get into PS2 homebrew, and it works well. But even with its $200 pricetag, my opinion is that the PS2/Linux kit offers a whole lot more.

My personal preference? I currently use Naplink and PS2LIB for all of my PS2 dev work. My recommendation was more for those who haven't got a lot of experience with PS2 hacking, and are looking for the easiest and most documented entry into the system.

<blockquote> Both the PS2DEV or linux kit is a great way to learn about the PS2 and develop software for it. I would highly recommend either getting the linux kit or getting involved with the PS2DEV community. </blockquote>

I agree wholeheartedly.


Survey

Favorite scripting language

  • Python
  • Perl
  • Tcl/tk
  • Shell
  • Other/obscure language ;-)

[ Results | Polls ]

Votes: 261
Comments: 5


- PR -


Login





 


 Log in Problems?
 New User? Sign Up!

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001-2007 by Codingstyle.com.
This web site is running Post-Nuke, a web portal system written in PHP. Post-Nuke is Free Software released under the GNU/GPL license.

You can syndicate our news using the file backend.php