GstMemory Flags

[Nicolas Dufresne]

Le jeu. 29 nov. 2018 15 h 14, Stirling Westrup <swestrup at gmail.com> a
écrit :

> I'm in the middle of implementing a new type of GstMemory and would
> like some clarification on the intended meaning of the
> GST_MEMORY_IS_PHYSICALLY_CONTIGUOUS flag. The help text essentially
> just repeats what the flag already says, and ignores the fact that any
> piece of allocated memory represented by a single address is
> NECESSARILY physically contiguous. So the flag appears to be
> inherently useless (and indeed, it appears completely unused in the
> gstreamer sources).
>
> My only guess at a likely meaning is that it marks the memory as being
> part of a larger contiguous piece of allocated memory, but without
> additional associated information, this would appear to be of no use,
> especially considering that GstMemory already has a mechanism to
> handle this very thing, using the size and offset fields.
>
> So, what is the flag intended to indicate?
>

It was meant to announce if memory is contiguous in physical memory.
Information known with NXP Freescale vendoe stack, but not generally
available for Linux CMA allocation. In general, you should not need it.


>
> --
> Stirling Westrup
> Programmer, Entrepreneur.
> https://www.linkedin.com/e/fpf/77228
> http://www.linkedin.com/in/swestrup
> http://technaut.livejournal.com
> http://sourceforge.net/users/stirlingwestrup
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20181129/c556c428/attachment.html>