This is the topic for those starting out on the PS2. Ask questions and they shall be answered.
I made the topic so that those browsing through here would have something to look at. Those people at #ps2dev can only answer the same question so many times before going nuts.
I will be making a lot of references to the GBA since its a commercial console I know. Anyway, here's the first question, not sure how to say it, but here it goes.
What do you have to do when programming the PS2?
I know that question sounds general but let me give you an example. Like on the GBA, you set X register to control the display and read from X register to get button and d-pad input. Is that the same on the PS2? For consoles in general?
Thanks..
The newbie topic
The newbie topic
while (your_engine >= my_engine)
my_engine++; :P
my_engine++; :P
Consoles in general? Yes.
On the PS2? Not really. :)
Most IO on the PS2 is done by another processor for you. A command is sent to that processor, say to draw a poly on the screen, and it does it for you leaving you free to do something else. Its a bit harder to get going in the first place, but once you do it makes sense. Mostly. Its a strange new way to do things, but its the way of the future.
If you look in $PS2LIB/ee/sample, you can see samples for how to write some text to the screen or read from the pads. Also take a look at gslib ( http://ps2dev.org/files/gslib_0.51.zip ), in case you haven't read the response in the other thread yet.
On the PS2? Not really. :)
Most IO on the PS2 is done by another processor for you. A command is sent to that processor, say to draw a poly on the screen, and it does it for you leaving you free to do something else. Its a bit harder to get going in the first place, but once you do it makes sense. Mostly. Its a strange new way to do things, but its the way of the future.
If you look in $PS2LIB/ee/sample, you can see samples for how to write some text to the screen or read from the pads. Also take a look at gslib ( http://ps2dev.org/files/gslib_0.51.zip ), in case you haven't read the response in the other thread yet.