On Mit, 2013-12-25 at 15:19 -0800, Mark Mueller wrote: > > ---------- Format Base Type P: Packed ---------- > MESA_FORMAT_[[component list,bit width][storage type*][_]][_][storage > type**] > * when type differs between component > ** when type applies to all components > > > examples: > MESA_FORMAT_R5G6B5_UNORM /* RRRR RGGG GGGB BBBB */ > > MESA_FORMAT_B4G4R4X4_UNORM /* BBBB GGGG RRRR XXXX */
This is slightly confusing in that the PIPE_FORMATs use this convention for naming the components of 'array' formats, packed formats use BGRXnnnn (just like packed MESA_FORMATs do now). Beware that not all PIPE_FORMATs have been updated yet according to that distinction. I'm afraid there also needs to be a way to encode endianness, either explicitly or via something like _REV to indicate the inverse byte order of the host byte order. This would apply to the packed values as a whole and to any multi-byte components of array formats. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
