On Wed, 26 Jan 2005, Michel [ISO-8859-1] Dänzer wrote:
On Wed, 2005-01-26 at 13:36 -0500, Vladimir Dergachev wrote:
Correction - I looked at the source and we compile the texture data as a string, so no conversion is being done.
Define 'compiling as a string', but it sounds to me like it does implicitly produce the same byte order regardless of the CPU architecture.
Yes. I meant that RGBA picture is represented as an unsigned char array. So byte 0 is always R, byte 1 G, and so on - irrespectively of the architecture.
There is however an issue of whether conversion is being done when doing memcpy from AGP space to the framebuffer.
best
Vladimir Dergachev
-- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
