search for: is_power_of_two

...r alignments and >> orientation. And if we say that bpp==12 means NV12, it will be a >> problem for all other cases where bpp==12 makes sense. > > I feel I still don't quite understand. Can't we define and document > CREATE_DUMB like this: > > If (bpp < 8 || is_power_of_two(bpp)) > ????bpp means bitsperpixel > ????pitch is args->width * args->bpp / 8, aligned up to > driver-specific-align > else > ????bpp is a legacy parameter, and we deal with it case by case. > ????list the cases and what they mean > > And describe that when allocating...

...rains in the scanline and buffer alignments and > orientation. And if we say that bpp==12 means NV12, it will be a problem > for all other cases where bpp==12 makes sense. I feel I still don't quite understand. Can't we define and document CREATE_DUMB like this: If (bpp < 8 || is_power_of_two(bpp)) bpp means bitsperpixel pitch is args->width * args->bpp / 8, aligned up to driver-specific-align else bpp is a legacy parameter, and we deal with it case by case. list the cases and what they mean And describe that when allocating subsampled buffers, the caller must adjust the wid...

...t; orientation. And if we say that bpp==12 means NV12, it will be a >>> problem for all other cases where bpp==12 makes sense. >> >> I feel I still don't quite understand. Can't we define and document >> CREATE_DUMB like this: >> >> If (bpp < 8 || is_power_of_two(bpp)) >> ????bpp means bitsperpixel >> ????pitch is args->width * args->bpp / 8, aligned up to driver- >> specific-align >> else >> ????bpp is a legacy parameter, and we deal with it case by case. >> ????list the cases and what they mean >> >>...

Hi Am 15.01.25 um 13:06 schrieb Tomi Valkeinen: > Hi, > > On 15/01/2025 13:37, Thomas Zimmermann wrote: >> Hi >> >> >> Am 15.01.25 um 11:58 schrieb Tomi Valkeinen: >> [...] >>>> These are all good points. Did you read my discussion with Andy on >>>> patch 2? I think it resolves all the points you have. The current >>>>