forums.ps2dev.org

[Actarus]

Hi all,

Im working on my emu and Im writing the code about the VFPU. On this http://hitmen.c02.at/files/yapspd/psp_doc/ I found these opcodes

[Raphael]

Yes. You might also want to take a look at binutils/opcodes/mips-opc.c and binutils/opcodes/mips-dis.c.
And for VFPU instruction documentation, in case you didn't already find it, there's the VFPU diggins thread by hlide, MrMrICE and me.
_________________
<Don't push the river, it flows.>
http://wordpress.fx-world.org - my devblog
http://wiki.fx-world.org - VFPU documentation wiki
Alexander Berl

[Actarus]

Thanks for help, but where? SVN? It doenst work.
But for VFPU opcodes that uses the matrices is it the first value?
_________________
Sam PSP Emulator
:)

[Raphael]

Binutils itself isn't on the SVN, just the patch. It gets downloaded when you install the toolchain and is then within psptoolchain/build/binutils-2.16.1.
If you don't have the toolchain installation folder any more, you have to download binutils seperately and extract it and apply the patch.
Therefore, just download the toolchain script and do the following:

[Actarus]

ok thanks again, I have another question with this ASM instruction

[hlide]

if i remember well :

[Actarus]

I tried qith this examples but it shows only zero, why? Can you help me?

[hlide]

I'm at work : no psp.

So the following code is untested :

[hlide]

...

[Pirata Nervo]

o.O
why did you post "..." ?
lool
_________________

Upgrade your PSP

[Actarus]

it doesnt work, with aligned and unligned memory.
_________________
Sam PSP Emulator
:)

[hlide]

please elaborate :

- what do you want to do exactly ?
- what doesn't work precisely ?
- what do you get instead ?

EDIT: or give us the assembly output of this code (use prxtool or psp-objdump on .elf file)

[hlide]

[Actarus]

I dont know but if i write this it doesnt work,

[hlide]

okay, there is no bug. It is just you don't know how asm constraints work :

- "m" : memory reference (and not pointer !), so you must use "=m"(mtx) or "=m"(*pf) in asm volatile ("usv.q %1, 0 + %0" : ...);

- "r" : register (which can be a pointer !), so you must use "=r"(&mtx) or "=r"(pf) in asm volatile ("usv.q %1, 0(%0)" : ...);

be sure pf really points on &mtx. I use "usv.q" instead of "sv.q" to discard the 16-byte alignment requirement.

[Actarus]

may be but form main.s (the asm file from gcc)

[hlide]

now it should work, right ?

[Actarus]

yes now it works with aligned and unaligned memory. OMG now it works also with O2.
_________________
Sam PSP Emulator
:)

[Actarus]

Again :) where can I find all VFPU opcodes? And their funcs?
_________________
Sam PSP Emulator
:)

[Raphael]

[Actarus]

thanks I found it but your site is very confused ;)

http://wiki.fx-world.org/doku.php?id=general:cycles and http://forums.ps2dev.org/viewtopic.php?t=6929. The search button doesnt work :( google is better.
_________________
Sam PSP Emulator
:)

[Actarus]

I have another question but for vcmp f1,rs which are the conditions?

[Raphael]

1st char:
E = Equal
N = Not Equal
2nd char:
Z = Zero
N = NaN
I = Infinity
S = Inf OR NaN
_________________
<Don't push the river, it flows.>
http://wordpress.fx-world.org - my devblog
http://wiki.fx-world.org - VFPU documentation wiki
Alexander Berl

[Actarus]

Thanks again you are very patient :)
_________________
Sam PSP Emulator
:)

[Actarus]

Another question now on vcmp.* and VFPU_CC, I have this code

[hlide]

hummm, 1 is not a good candidate.

use 0x40000000 (2.0) instead of 1 (denormalized number).

By the way, try to add 7 nop between vcmp.s and mfvc. Maybe one would be enough.

The reason why you got some weird numbers is because normally you cannot use the result in VFPU_CC immediately after a vcmp as it is not interlocked, so instead of reading the new value, you're reading the previous value.

Initially, VFPU_CC is 0x0000003f.

1) vcmp.s NZ 1 => X = 1, OR = 1, AND = 1, so you'd expect VFPU_CC = (VFPU_CC & (~0x31)) | (0x31). But you get 0x3f which was the previous value.

2) vcmp.s NZ 0 => X = 0, OR = 0, AND = 0, so you'd expect VFPU_CC = (VFPU_CC & (~0x31)) | (0x00). But you get the same value (0x3f) as expected in 1) because you're reading the previous value too early.

3) vcmp.s EZ 1 => X = 0, OR = 0, AND = 0, so you'd expect VFPU_CC = (VFPU_CC & (~0x31)) | (0x00). But you get the same value (0x0e) as expected in 2) because you're reading the previous value too early.

4) vcmp.s EZ 0 => X = 1, OR = 1, AND = 1, so you'd expect VFPU_CC = (VFPU_CC & (~0x31)) | (0x31). But you get the same value (0x0e) as expected in 3) because you're reading the previous value too early.

[Actarus]

For vcmp.s EZ,S000 with S000 == 2 it returns 0xE I think it's good, but form same values with vcmp.q NZ,R000 it returns 0x3F, why?

EDIT :

OK solved, i didnt initialize the matrix OMG it happens :)
_________________
Sam PSP Emulator
:)