On Sun, 30 Dec 2001, hzeng wrote:
> Hi,
> I add a attribute XV_AlLLOC_FB to use the fb managet to allocate a block of
>offscreen memory for
> other useage. And I also define a attribute XV_FREE_FB to free the video memory. But
>when I use in
> the app, the XV_ALLOC_FB can do, but the XV_FREE_FB can do nothing, the setattribute
>cannot reach
> to the case of XV_FREE_FB. I check the code, it same as all the other attributes in
>Xv, but I cannot
> find where is the trouble.Do you know what reason can make the Xv cannot realize a
>atom ?
>
There's really not much checking done by the higher level code.
Atoms are just 32 bit cardinal numbers that correspond to a text
string. Any valid atom sent by the client via XvSet/GetPortAttribute
will make its way into the driver unless the client passed
incorrect parameters to XvSetPortAttribute. In every case,
the client would be sent an error. Is the client receiving
an error? Is it making into your driver's SetPortAttribute
function at all?
Mark.
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
