forums.ps2dev.org

sashz wrote:update 20091201 ;)
gcc4.4.2 devtools and webkit based browser (less memory usage)

Thanks for the update :)

A recent patch appears to have resulted in ps3vram performance above what was previously achieved.

Nice work :)

Both those still need quite a bit of work, and neither will do much for video playback.

For HD video, faster h264 CABAC decoding is what is needed.

I can't see why that video would be a problem...

Sorry, I have no more suggestions for the time being.

I recall there being some problem with setting fullscreen from the command line - does it work if you press F while the video is running?

Getting it to precisely match a Sixaxis would be really useful if you want to make a "man-in-the-middle" type device that would allow a computer to manipulate real Sixaxis input before sending it to the PS3. (Just imagine all the cool tricks you could do with that while playing games...) ...

-ao alsa should work - do you see any errors if you try it?

I've tried several different 720p and 1080p mp4 and mkv contained videos - nothing plays fast enough with -vo sdl:driver=PS3.

-vo fbdev is significantly better for the 720p mp4 I tried. Still dropping frames in places, but mostly watchable.

You need to specify the SDL driver mplayer -vo sdl:driver=PS3 moviefile Seems to be working for me. I say seems to be because the PS3 is currently headless - without the PS3 driver I see mplayer with ~100% cpu utilisation. With the above, I see ~80% CPU (fluctuating) and two SPU processes li...

basically writing a software rasterizer on my pc using SDL, which will eventually port to ps3 using the framebuffer, but im trying to think forward when it comes to efficiency, my render list i want to be able to depth sort etc etc, and im not sure if using template'd functions like STD vector work...

[nevermind]

Odd, then, that Sony employee Geoff Levand would state on IRC then that it was unintentional broken in the FW update.

The last I'd heard, ps3vram was buggy and unsafe anyway. See http://ozlabs.org/pipermail/cbe-oss-dev ... 05513.html

ps2devman wrote:To be totally complete (thx to sandworm who reported it in linux forum -link below), be aware that JimParis contribution to geoff kernel (ps3 ram extended thru gpu ram) has been officially (and silently as usual) shutdown in fw 2.50.

"Officially"? I doubt it.

'TwosComplement'

It is quite likely that your screens are actually not displaying the 5-10% of missing pixels - it's a common problem, and tends to not be detectable in general within the GameOS or HD movies. This is definitely not the case. All 720p / 1080i / 1080p screen modes are fully displayed in GameOS, on bo...

It is quite likely that your screens are actually not displaying the 5-10% of missing pixels - it's a common problem, and tends to not be detectable in general within the GameOS or HD movies. Some screens have a "dot for dot" or similar setting which can, in some circumstances, help get fu...

Also, xf86DrvMsg(pScrn->scrnIndex, X_INFO, "Image Processed\n"); in spu_video.c results in a lot of noise in /var/log/Xorg.0.log

32bit works for me. For some reason, my xorg-server didn't like the _ in the driver name (kept looking for spufbdev), and renaming the driver to spufbdev_drv.so didn't work as the entry point is derived from the file name, so I replaced all spu_fb with spufb (and SPU_FB with SPUFB) in spu_fbdev.c Al...

Let me know if you need a beta tester.

I'm currently thinking that the harness should provide the following: * Access to one or more SPUs (different compos could have different SPU limits) * Access to a sound buffer in main memory (44.1KHz, Stereo, 16bit?) * Access to a frame buffer in main memory (640x480 32bit colour?) I'd like to see...

I've been thinking about PS3 demos for a while. Not using 3D acceleration though, but that's just because when I was first considering it there was no 3D hardware support of note. SPU program, one SPU only, using SPU local store only - no DMA read from main store, no write (apart from video/audio ou...

Have you tried either Ctrl-L or (if you can still type) running 'reset'?