forums.ps2dev.org

Apologies for not replying, I didn't see this message until now. Since I've largely given up on PS2 development and have moved from SVN to GIT, I wasn't in a hurry to get that site back up. I have now created a repository for apascan on github instead.

http://github.com/chewi/apascan

I was on and off about continuing it, now I'm pretty much off, unless as I've said before, some who REALLY knows this stuff steps up to help. I don't see that happening.

We need to agree on the machine names or we're going to get in a mess. Just mips is okay for the IOP since it is a very generic MIPS. mips64r5900el is the official name for the R5900 according to the latest config.sub . It is important to follow this file because other packages include config.sub fr...

I never patched config.sub because Gentoo automatically replaces it with the latest version when building.

I've just moved house and am on a very slow connection for the moment. I'll be running a server from next month and so I could host if necessary. I very highly recommend Git over Subversion though. I know Git can seem scary at first but I used Subversion for years and haven't looked back since I swi...

Well spotted. mipsel is just generic Little Endian MIPS. Oh well. :(

I'm a bit puzzled by that. I know Ed got NetBSD 2 going a long time ago but I thought nothing had been done since due to the toolchain. The official page says as much and it even links back to this place.

http://www.netbsd.org/ports/playstation2/

I don't know where you got that from. The most we've seen from 2.6 was the first line of output. That was built with an almost vanilla GCC 4. It was almost like booting a regular MIPS Linux kernel with a PS2 graphics driver and expecting it to work. It wasn't that remarkable really. I doubt you can ...

GCC 3.0.4 is the latest for PS2 Linux. GCC 3.2.2 is the latest for PS2 home brew. Both of these are too old. I've been working towards GCC 4.3 for both but the only thing it builds and runs without any issue is the "stars and text" demo.

I think we really need a MIPS guru to take us through these last few steps with the toolchain but I admire your enthusiasm. I didn't know much more than you did when I started on this. You'll need to know some MIPS assembly. I tried to tinker with GCC before learning this but, in truth, I didn't rea...

I'm afraid it's the differences between the PS2 and regular MIPS machines that are the problem so having access to other MIPS hardware doesn't really help very much. I've wondered whether a PS2 emulator would help instead. I think I did get the stars demo running through PCSX2 at one point. If I rec...

Sorry, I've had further problems with my server that are beyond my control. I'm going to start hosting it myself next month. I've uploaded the binutils patches somewhere else in the meantime.

http://dev.gentooexperimental.org/~chew ... 15.tar.bz2

Sounds like you have some wider experience than I do. I'm also a Bachelor of CompSci but we didn't do any actual assembly. I did a language and compiler design module but we ran out of time just before getting to the assembly part and that would have been SPARC anyway. Still, it proved useful. I end...

I think this was the last patch I did against 2.4.17. I haven't touched that stuff in a very long time. Getting GCC 4 to work was more important. I didn't release any of it officially because I wanted to fix the USB stuff properly. You could just dump the MontaVista code in there if you wanted to th...

I tried to contact Ed over two years ago through the Gentoo forums but he never read the message - it's still sitting in the outbox. That patch is against the old toolchain and contains just the stuff to handle the short loop length bug. If you were willing to sacrifice performance by only building ...

Thanks man. Regarding Linux, I have generally preferred the option of moving towards 2.6 rather than sticking with 2.4 because 2.4 has traditionally not compiled with GCC 4. However, I just discovered that changed with 2.4.34. The fixes for MIPS weren't included in that release but they were mention...

Hey guys. You probably took my server being down as quite a bad sign but actually it's only been down for a week due to it being moved. It's just come back up. As for me, life took over with getting married in May and trying to buy a house now. Unless anyone who seriously knows what they're doing ca...

The suggestion came from this bug . I've just had a look through the files to see what's going on. asm/byteorder.h includes linux/byteorder/little_endian.h and that includes linux/types.h. This defines types such as loff_t but only when __KERNEL_STRICT_NAMES is false. At this point, it is false so t...

That package appears to be the correct one. I did a little digging and found a similar issue. Try moving the "#include <sys/types.h>" line to the top of the list of includes in apascan.c. Let me know if this works.

Haha. We have enough trouble trying to run Linux on the bloody thing, nevermind AROS! I did try it on my PC once. I'm surprised it gets as much attention as it does. I'm personally more excited about OS4. Let's hope something good comes of that lawsuit.

What I'm saying is that you can't type directly into the emulator window with your keyboard. There is only a pad plugin at the moment. They'd need to write a USB plugin that can fake a raw keyboard since the actual keyboard would already be in use by the host operating system.

News! Firstly, I've ditched the 128-bit stuff for now. It wasn't working out and it's just not needed. Maybe I'll revisit it sometime or someone else can have a go. Secondly, I have a confession to make. Everything is suddenly working a lot better. I've thrown three MP3s at madplay and it plays all ...

First of all, as it says in the README, apascan won't handle drives larger than 127GB. The official APA format doesn't support this and larger sizes were only achieved through the 48-bit LBA hack and the ToxicOS APAEXT format. I'd like to support them but I don't have any drives larger than 120GB. Y...

If anyone's interested, I've just made a commit. This is the first one I've made in a long time. You'll need a recent version of Portage because I've removed the separate digest files.

RESULT!! I got madplay to make some sound!! :D We're not there yet but this is very encouraging. I decided to track down exactly where madplay was failing using some humble printfs. I didn't realise that madplay carried its own copy of the isjpcm IRX and it was the loading of this module that was fa...

I've just been trying to run RadShell inside PCSX2 in the hope that I can shed some light on the problems I've been having with GCC 4. If I simply start it with Load ELF, RadShell starts but it says that it cannot open /home/chewi/radshell/radshell.rsh. I thought PCSX2 would provide access to the fi...

Good news. I've got GCC to build for the first time in months. I had trouble with it ever since I started adding 128-bit support. The bad news is that madplay doesn't behave any differently. I'm not sure if it's using the 128-bit stuff at all. There are 128-bit instructions in the resulting binaries...

If I remember rightly, the sound code in sdldoom is quite hacky. I'm not surprised it doesn't work. I think the guy was trying to make it so that sdl_mixer would not be a requirement or something like that. I also tried to play a network game between a PC and a Mac using sdldoom once and it failed d...

Smart, I didn't know about that! Not that I was going to try it myself but it's good to know. Thanks.

Booting wirelessly in general is quite hard and a quick search didn't turn up anything. Since wireless generally needs stuff from userspace in order to work, you'd need to put the necessary programs and libraries on an initrd/initramfs. I wouldn't bother trying this with Linux 2.4 and 2.6 on the PS2...