> I've also been playing with some mmx-ification of the XVideo routines,
> for example I also did an SSE-4:2:0-to-4:2:2 function.
I just did this too, MMX only though. How many cycles/pixel did you
end up with? What percentage of pairing did you achieve?
> There was some discussion on #xfree
Daniel Secrieru wrote:
[snip]
> I had a lot of problems with incompatibilities between the two and this
> clipbox stuff is the latest. In Win32 there is a function called GetClipBox,
> that does the following (quote from MSDN):
>
> 'The GetClipBox function retrieves the dimensions of the
"Sottek, Matthew J" wrote:
>
> XV_FRAME_TYPE = XV_HOLD
> XvShmPutImage()
> ...
> XvShmPutImage()
> ...
> XvShmPutImage()
> XV_FRAME_TYPE = XV_FRAME
>
> The target of the XvShmPutImage will only change when XV_HOLD is
> set. (Or if XvShmPutImage is called without XV_HOLD) So however
> many XvShmP
"Sottek, Matthew J" wrote:
>
> >"Sottek, Matthew J" wrote:
> >>
> >> Here is the proposal again, if there are on complaints I'll
> >> implement it this way.
> >>
> >> #define XV_HOLD 0x0
> >> #define XV_TOP_FIELD0x1
> >> #define XV_BOTTOM_FIELD 0x2
> >> #define XV_FRAME(XV_TOP
"Sottek, Matthew J" wrote:
>
> Here is the proposal again, if there are on complaints I'll
> implement it this way.
>
> #define XV_HOLD 0x0
> #define XV_TOP_FIELD0x1
> #define XV_BOTTOM_FIELD 0x2
> #define XV_FRAME(XV_TOP_FIELD | XV_BOTTOM_FIELD)
Just to clarify, the default
Mark Vojkovich wrote:
>
> On Fri, 19 Oct 2001, Pranay Kumar wrote:
> >
> > It would indeed help if Xv could be used to hardware scale RGB surfaces.
> >
>
>One thing I've never been clear on is what the FourCC codes
> for RGB surfaces are supposed to be. I'm not sure where to
> find standard
