In article <[EMAIL PROTECTED]>,
Stelian Pop <[EMAIL PROTECTED]> wrote:
>
>Well, not quite... I've had several X lockups while using the YUV
>acceleration code. Let's say one lockup per half an hour.
Strange. I've watched DVD's etc. Maybe it's not the Xv code, but your
camera code?
>Even the performances are controversial: with 320x240, I achieve
>great performance with xawtv/meye driver, I can even use the hardware
>scaling facilities (well, the xawtv sources need a little hacking for
>that), but in 640x480 the framerate achieved with Xv is below the
>one I get by converting YUV->RGB in software...
There's something wrong with your setup. I watch full-screen DVD's on my
VAIO. It's not really fast enough with just the YUV conversion done in
hardware (it's plenty fast enough if MC and iDCT would be done in HW
too, but ATI doesn't release docs without strict NDA's). But there's no
way DVD's are watchable with sw YUV conversion and scaling.
>But the main question remains: does the MotionEye camera support
>overlay or not ?
That one I have no clue about at all.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/