> x = curent_destination_byte;
> z = x & 0111b
> x = z | y
> You have to do this to do every single pixel write with 15bit color. With
> 16bit color all the bytes are even so it's just
> dest = val;
No. Depth 15 is stored in the framebuffer at 16 bpp; i.e. there's one
pixel per 16 bits, wit
> Why not use depth 16?
Because pink is not my favourite shade of gray.
Juliusz
On Tue, Sep 10, 2002 at 11:19:23AM +0200, Eduard Bloch wrote:
> #include
>
> I have a problem with recent Xfree86-4.2.0 and .1 pre debs (IMHO since
> 0-0pre1v3 or so). After few hours of intensive working, Xfree needs more
> and more memory even after closing (or killing) every X application, it
>
> Why not use depth 16?
>
> AFAIK depth 16 is a 2 bytes not much difference from 15 (almost 2 bytes)
> what makes it worth over depth 16?
In memory if you want to write bits that don't fit nice on a byte, you
have to,
y = 10101b; /* or however you specify 5 bits you want to go at the
begining o
On Tue, Sep 10, 2002 at 11:57:27AM +0200, Juliusz Chroboczek wrote:
>
> http://www.pps.jussieu.fr/~jch/software/files/analyse-x.pl
>
Why not use depth 16?
AFAIK depth 16 is a 2 bytes not much difference from 15 (almost 2 bytes)
what makes it worth over depth 16?
--
Carlos Barros.
http://www.pps.jussieu.fr/~jch/software/files/analyse-x.pl
On Tue, Sep 10, 2002 at 11:19:23AM +0200, Eduard Bloch wrote:
> I have a problem with recent Xfree86-4.2.0 and .1 pre debs (IMHO since
> 0-0pre1v3 or so). After few hours of intensive working, Xfree needs more
> and more memory even after closing (or killing) every X application, it
> keeps lots of
7 matches
Mail list logo
