forums.ps2dev.org

First of all, no I did not upgrade, I'm still using 2.01. However a friend of mine (posting as tgnard here) has upgraded to 2.1 and is interested in getting the RSX back; so we can compare the behaviour of the HV on the two boxes. @ps2devman, yes maybe the new call is a second part of some setup. Al...

Do not patch your kernel, use the ps3rsx module instead. For this to work you need FW <= 2.01. I'm still looking at a way to workaround the video ram limit enforced in FW 2.1. Here is the current status: - Calling lv1_gpu_memory_allocate with bits 52-63 set works and bypass the size check. However p...

Interesting.. The 'channel' number does not correspond to 'RAM channel', it is the hardware context number (see http://nouveau.freedesktop.org/wiki/ContextSwitching). The ps3rsx module creates a context for itself on startup, and then creates another context when a user mode application opens /dev/f...

IronPeter, I honored my promise, your christmas present is waiting for you in libps3rsx svn. To FW 2.1 users, you can try this new libps3rsx version, with patched ps3rsx module as above (1ULL << 60 trick) and report if it works or fails. The dmesg log looks promising to me... Rex_VF5, Linux does not...

hermes: do you mean it does not return -17? If correct, this is great news as we basically have a fix for the 2.1 FW issue until it gets patched again. Can you paste the dmesg log?
Also can you check Xorg runs fine in this case?

Hi, I've been working on improving the existing ps3vram driver with our recent RSX discoveries. Basically it is possible to ask the RSX to perform DMA XDR system memory to DDR video memory and vice versa. Using DMA is _much_ faster than accessing the ioremapped video memory directly. However relativ...

Hi all, So it seems the hunt season has started again.. I have just noticed that the lv1_gpu_memory_allocate call ignores the highest bits (52-63) of the ddr_size argument in FW 2.01. So I have some little xmas holiday homework for people with FW >= 2.1. Please try changing the following in the ps3r...

@Panajev2001a, the kernel module output looks good. I have the same here except for the RSX revision (11), I guess my hardware is older (european 60GB version). The new ps3fb reserved size should not be an issue, I'm using 1920*1080*2 bytes for Xv at most and the rest for upload/download to/from scr...

Hi, I've just committed the updated ps3rsx module and Xorg driver: git clone http://mandos.homelinux.org/~glaurung/git/ps3rsx.git git clone http://mandos.homelinux.org/~glaurung/git/xf86-video-ps3.git I've tested it under the following configurations: - geoff's 2.6.24-rc3/gcc-4.2 1280x720p full - De...

Just as a quick note, IronPeter, I got your (impressive) troll rendered from second context using new ps3rsx module (updated to /dev/fb1 API). I'll cleanup and post that tomorrow, time to sleep now.

@mickfromperth, I noticed some corruption too when trying the module with the original Debian 2.6.16 kernel. In my case, it is due to the ps3fb driver not working the same at all as it does now. In particular, assuming the fb base is the same as what is seen by the RSX at GPU_IOIF is wrong. Can you ...

Here is a draft of the separate kernel module: git clone http://mandos.homelinux.org/~glaurung/git/ps3rsx.git I've updated the Xorg driver accordingly: git clone http://mandos.homelinux.org/~glaurung/git/xf86-video-ps3.git It is not yet finished, and mostly untested, but it shows my plan for the int...

Thanks for testing mc, it's good to know that this 2.01 was not a RSX/HV fix release :-) Just a little update on kernel module before sleep: I just managed to get Xorg running with the separate module (there were a lot of hardcoded values that were broken if running in a different context). I quickl...

Hi, Separate kernel module is not ready yet, it seems a call to fb_blit (from any context, and even of 0x0 size) is still needed to kick off the fifo. So as soon as ps3fb blit is disabled with PS3FB_IOCTL_ON, it does not work. I'm confident I can work something out in a few days though. Concerning t...

Tracking geoff's tree will always be problematic. Now that I know it is possible, I'll provide a separate kernel module for the GPU stuff. Another solution would be to have our own ps2dev git tree for the kernel. If we are going to make an easy to install CD for 3D development, as suggested, we will...

Hi, 2. ) Indeed xoff and yoff are not important. The actual size of the display cannot be obtained from standard framebuffer API, only the size of the region copied to VRAM by the blitter (which may be smaller in non-fullscreen mode). What I do in the Xorg driver is I ask the ps3fb its current video...

Hi, I've finally been able to setup and use a second independent context. I was able to perform the 'upper VRAM workaround' from this second context, even though the first context (setup by ps3fb) has restricted upper VRAM access through DMA (by means of the lv1_gpu_memory_allocate(ps3fb_videomemory...

Also note you cannot mix both the Xorg accelerated driver and the ps3gpu test program yet. The reason is we share the same FIFO and hardware context for now. The hardware has capability for 8 differents contexts so we could allocate for example one for Xorg, one for libGL and one for swap over VRAM,...

IronPeter, I've been looking at the separate module option and I don't think that's the best approach finally. Recently the call to lv1_gpu_memory_allocate in ps3fb.c has been changed to: status = lv1_gpu_memory_allocate&#40;ps3fb_videomemory.size, 0, 0, 0, 0, ...&#41; That means if we want ...

Yes that's be nice :-) I didn't look into interrupts yet, there is probably some valuable info there. So, I just retested FB_SETUP before fifo is trapped, and I still get the busy return code. Maybe I'm doing something wrong, so if you manage to have a second context, I'll be interested to know how....

Hmm, yes, maybe that's the problem. Did you manage to setup a fully working second context?

I agree we need a separate module for easier setup. I would prefer to have a totally independent second context with its own fifo, but we don't know how to do that yet. The second call to lv1_gpu_context_allocate does provide a different dma_control area but the values are all zero. A call to lv1_gp...

Hi all, I'm back looking at HV calls, here are the findings of the day: - lv1_gpu_context_allocate has flags as second parameter, it creates some interesting RSX DMA objects when set to 4 and 8. In particular objects created by setting flag to 8 are very interesting as they target system memory: key...

I've just noticed that since lpar_reports correspond to VRAM at address 254MB, DMA notifiers created by the HV are available from Cell. I've updated the wiki accordingly. That means we don't need to create our own DMA notifier objects in RAMIN, we can just use the ones provided by the HV to monitor ...

cnlohr, excellent video! I've some news on the Xorg side. I've update the driver with basic SolidFill acceleration, fixed an synchronization issue with DownloadFromScreen/UploadToScreen, and added support for non-fullscreen video mode. There was also a patch from ReneR to fix driver crashing on 64-b...

Hi, Falcon, IronPeter, keep in mind that in non-fullscreen mode there are actually black borders in video ram to account for missing image parts on standard TV, therefore the pitch of virtual FB and video RAM FB may be different. The accelerated Xorg driver does not handle non-fullscreen mode proper...

Hi, For those interested, I've managed to get some time to update my experimental xorg based on IronPeter's and the nouveau team work. It now supports a lot more Composite operations, including alpha blending, through the 3D engine. That means accelerated translucent windows, and it works with Xv to...

Well done IronPeter! I've just been playing a bit with your code, drawing quads, using integer instead of float vertices, etc.. I'm wondering why color does not work, but I think I'll play with texturing first (based on nv40_exa.c blending code). Congratulations!

IronPeter, you mentioned 'multiply blits' earlier, did you manage to get that working? The problem I have with blending is that if I change the blit operation from SRCCOPY (3) to BLEND (2) it hangs the GPU. I think that's why the nouveau guys implemented the EXA composite operation using a textured ...

Hi, Here is an update of the GPU based Xorg driver, with accelerated Xv support: git clone http://mandos.homelinux.org/~glaurung/git/xf86-video-ps3.git This patch to the PS3 Linux framebuffer driver is needed to test the Xorg driver: http://mandos.homelinux.org/~glaurung/ps3/20071025/ps3fb.diff Xv s...