On Monday 10 March 2008 14:39:04 Stanislav Brabec wrote: > Tim Chick wrote: > > OK, the c1000 and c3x000 NATIVE resolution is > > > > 480x640 - 480 WIDE by 640 HIGH, NOT 640 wide by 480 high. > > > > So when you encode a video at 640x480, and try to play with -vo pxa, it > > will try to open a framebuffer of size 640x480, which is too big, as > > the biggest supported is 480x640. > > Trying to play 480x640 video using pxa driver enters my Z into dead > swapping mode. 240x320 plays perfectly. >
I wonder if that's simply because you run out of RAM? I keep on saying that you will only have much luck with resolutions not much higher than 320x240. PAL VideoCD is fine, but don't go any higher, > > as the zaurus DOES NOT have the cpu to play > > 480x640 movies at a good frame rate - so there is no point. > > When I am trying to play 480x640 video using fbdev, it performs very > badly. But the last few seconds plays smoothly. > > It indicates, that the problem may be decoding of the video, not the > playback itself. Also comparing of -vo fbdev and -vo null or so may > indicate, that 70% of the CPU time may be spent by video decoding. > Yes, this is what I mean - there is not enough CPU to both decode the video and display it. You can try this with -vo null. Also, the SDRAM bus uage goes up too high when both overlays are enabled at 100Hz, so video decoding takes longer than it would. > > 2 - when using 480x640 resolution, the refresh rate is set to be very > > high. > > I think it may be a bug. In Angstrom I see weak artifact few pixels > above any edge. Diag mode and Sharp ROM does not have this problem, and > I guess they use significantly lower frequency (refresh rate is even > visible). > Yes - but this has been around for ages - there was some mailing list traffic about it years ago from Richard P - the refresh rate is over 100Hz for 480x640 mode - which is apparently the same as the Sharp ROM. > > This uses much SDRAM bandwidth. Also the bottom layer screen > > depth is 16bit - again this uses lots of bandwidth - it could be > > reduced whilst playing moves full screen. This needs a new mode added > > to the kernel, and maybe a change to the pxa fb driver to allow the > > depth to be changed without freeing the screen buffer. > > Isn't there any way to turn on mode 240x320 with hardware scaling? How > did it Sharp ROM? > There is no hardware scaling. If you use -vo pxa -vm it will alter the clock generation of the device to "double" each pixel size, so 320x240 video will play nicely, fullscreen, in Angstrom - the same way as it used to in Cacko etc. > > 3 - the current pxa mplayer driver enables the "text" overlay, used by > > mpalyer to draw the icons and time indications etc all the time. This > > wastes more DMA bandwidth. The driver needs to be updated to only > > enable this overlay (overlay1) when something is on screen. > > Very simple ugly work-around: Make terminal full screen and redirect > Eh? No, I need to update my mplayer driver to only enable overlay1 when needed. overlay1 is used by mplayer icons and text. overlay2 is the video overlay. The "base" framebuffer has the screen on it. Thanks, Tim _______________________________________________ Angstrom-distro-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
