Picasso96 PIP support

Hi everybody,

Figured while I was waiting for a working SDK I'd play around with overlay mode a bit.....

Can't get it to work, though. The documentation very helpfully says "See Includes for possible failure reasons". Which would be great if I could find anything at all anywhere.

The function I'm calling is:
mWindow = IP96->p96PIP_OpenTags( P96PIP_ErrorCode, &tError, WA_Left, 10, WA_Top, 10, P96PIP_SourceFormat, RGBFF_YUV422, P96PIP_SourceWidth, mPrefs->Width, P96PIP_SourceHeight, mPrefs->Height, WA_InnerWidth, mPrefs->Width, WA_InnerHeight, mPrefs->Height, WA_IDCMP, IDCMP_RAWKEY | IDCMP_MOUSEBUTTONS | IDCMP_INTUITICKS | IDCMP_NEWSIZE, TAG_DONE );

mWindow is set to NULL afterwards, and P96PIP_ErrorCode fills tError with 0x02. What this means I haven't a clue. It may mean that the Radeon hasn't had any breakfast today and doesn't feel like co-operating for all I know.
Is there better documentation on P96 PIP stuff? Or even examples anywhere?

Can anyone help? Ta!

@Spirantho

From what I see is that you use the wrong format, it's RGBFB_something not RGBFF_something. Additionally, the Radeon driver only supports RGBFB_YUV422CGX.

@Spirantho

Is the error code of type ULONG? If so, make sure that you use the right printf code for printing the error code (e.g. %lx), or the numbers you get won't make any sense.

Hans

@Spirantho

You need to tell PIP what screen to open on.

RWO

@rwo

That did it. I had to lock the workbench screen and pass the Screen * structure into the P96 call.

The debug string I used was actually a %p (as pointers are ULONGs aren't they?), but I changed it to %lx just to be sure and it still returned 2.

I now have a PIP window!

Is there proper documentation for this sort of thing? I can't find any info about needing to pass in the screen pointer or anything like that, nor about error codes. Error 2 therefore appears to be "Don't know what screen to use" and error 3 appears to be "PIP window already open".

I'm still stuck without DMA though. I was almost hoping that I could bypass AllocVecTags() completely and call StartDMA on the bitmap created by P96PIP_OpenTags(), but alas, no. Calling StartDMA on the PIP Bitmap just hung the machine solid.

Looks like I'm back to waiting on that SDK then.....

@Spirantho

The error codes are defined in "libraries/Picasso96.h".

@Spirantho

Quote:

As srupprecht said, it's in the header file (starting at line 385). And error codes 2 and 3 are given as:
Quote:

So you're right about those two.

Hans

Good good, I know where to look now!

Thanks for the quick help, guys....!