Would this program work well on ps2?

[danielb]

Hi,
Do you think this program can work on the ps2 (Single Player Game Transmitter) ?
Theres a client for linus but i dont know if the ps2 has enought power to decode xvid@ 480p and audio...
what do you think?

It would be a nice small gaming pc to have connected to the tv!
Between my dektop and laptop it works great!

[danielb]

I manage to compile it but it seems video output is still very slow...
would it work better on blackrhino?

[deba5er]

@danielb

The PS2 has enough power, but few of the optimizations are available in PS2 Linux. You have it compiled and working, which is a great first step, now look at the configure options for anything you can add (or remove) from the compilation, and see if it compiles with "-O3" as well.

[danielb]

1. What "-O3" does? Where i put it?
2. This program uses a lot of librarys: SDL xvidcore pthread celt "GENERICLIBS = -lSDL -lxvidcore -lpthread"
3. Probably it would do better on the blackrhino? Because video decode and x11 is working better than 2.6?
4. the 2.6 kernel already supports x11? I dont have a vga cable only component (Yellow,red,white)
5. Theres no way to make it as a ps2 elf?

[deba5er]

@danielb

1. What "-O3" does? Where i put it?

vi configure
You will be able to change "-O2" to "-O3" sometimes to increase optimization, so that the compiled program runs faster. This makes the compilation take much longer, and sometimes due to low memory on the PS2, it will not work.

3. Probably it would do better on the blackrhino? Because video decode and x11 is working better than 2.6?

It is quite likely that it will run faster on blackrhino with the 2.4 kernel. However, your compilation may not work because the compilers are very old.

4. the 2.6 kernel already supports x11? I dont have a vga cable only component (Yellow,red,white)

Yes, the 2.6 kernel supports x11 using a framebuffer video driver. It is EXTREMELY SLOW to boot to X-Windows though, as it is experimental, optimizations are not made yet.

5. Theres no way to make it as a ps2 elf?

Yes. If you can get it to compile as a native homebrew, it would likely run faster. However, you have much more work as all of those libraries you noted have to successfully compile with the PS2SDK, using the old version compiler. I think that for simplicity it is better to compile for Blackrhino, and try to optimize there.

[danielb]

Tried to compile to blackrhino but i keep hitting walls!
I cant even compile xvidcore it gives a bunch of error and quits! Needs more recent gcc?

lots of errors like this:
../../src/dct/fdct.c:199: warning 'mm1' might be used unitializaed in this funcion
and then fails:
make: *** [dct/fdct.o] Error 1

EDIT:Trying to use gcc3 from another topic you said:

I have never compiled gcc 3.03, but instead downloaded them like yourself as pre-compiled binaries. Here's where they are now:

Linux for PlayStation 2 Community: Project Info - GNU C Compiler

After extracting, I created a script /usr/local/bin/setgcc3 which has these two lines:

export LD_LIBRARY_PATH=/usr/local/gcc3/lib:$LD_LIBRARY_PATH
export PATH=/usr/local/gcc3/bin:$PATH

Running this script before compiling should setup the gcc 3.0.3 environment. There are most likely better ways to configure this, but this is the way that works easily for me.

But if i do after:
echo $PATH its the same as always
same for LD_LIBRARY_PATH
........

[deba5er]

@danielb

But if i do after:
echo $PATH its the same as always
same for LD_LIBRARY_PATH

That's very odd. You can always change /etc/profile or your local .bash_profile line which sets PATH, and then restart.

[danielb]

XVID CORE IS COMPILING GOOD!!!!!! Already passed the fdct.c file!
I must be doing something wrong in the script... typed that manually in the terminal and worked!

EDIT:Oh come on!!! another error!

/usr/bin/ld:libxvidcore.ld:1: parse error in VERSION script
collect2: ld returned 1 exit status
make: ***[libxvidcore.so.4.4]Error 1

Probably old binutils.. cant get to compile newer binutils...
Seems like i'm going to give up again....

[deba5er]

@danielb

Don't give up yet. That is very fixable. Give me a second or two and I'll edit this post with instructions.

Instructions:

su
vi /usr/bin/ld

Enter "/2.9" without the quotes (pressing enter after)
Press "n"

You will be at the second instance of 2.9 (version of ld). You must change "2.9-ee" to "2.9.ee" by moving cursor over the dash, pressing "r" and pressing "." Then ":wq!" without quotes and press enter.

You must then rerun ./configure and restart make. This should get you past this problem. Many configure scripts read the weird PS2 EE version of ld incorrectly because of an unexpected dash in the version number.

[danielb]

Im really getting mad with this!!!!!!!!!!!!
Now ./configure complains that C compiler cannot create executables!?!?!?!?! It worked before and now it doesn't!