From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <7d35ef7d04e9d09a457975b0c94d614c@felloff.net> References: <857f9916689796f5bb56cb65aa0afc12@hamnavoe.com> <7d35ef7d04e9d09a457975b0c94d614c@felloff.net> From: Dave MacFarlane Date: Mon, 30 May 2016 09:11:25 -0400 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=94eb2c05be56259d3305340f0022 Subject: Re: [9fans] More about /dev/draw Topicbox-Message-UUID: 95aa57fe-ead9-11e9-9d60-3106f5b1d025 --94eb2c05be56259d3305340f0022 Content-Type: text/plain; charset=UTF-8 Probably a typo, I was going from memory. I thought it was a multiple of 8 bits per component, not for the whole thing, so that (and a typo) would explain it. But the bigger problem was that even if you only have 1 bit for r, g, and b you should be able to represent yellow as 110, so any r>1g>1b>1 should be able to handle it. On Mon, May 30, 2016 at 5:27 AM, wrote: > 6+5+6 is 17, not 16 bit. is this a typo or was r5g6b5 ment? > > -- > cinap > > -- - Dave --94eb2c05be56259d3305340f0022 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Probably a typo, I was going from memory. I thought it was= a multiple of 8 bits per component, not for the whole thing, so that (and = a typo) would explain it.

But the bigger problem was tha= t even if you only have 1 bit for r, g, and b you should be able to represe= nt yellow as 110, so any r>1g>1b>1 should be able to handle it.

On Mon, = May 30, 2016 at 5:27 AM, <cinap_lenrek@felloff.net> = wrote:
6+5+6 is 17, not 16 bit. is this a= typo or was r5g6b5 ment?

--
cinap




--
- Dave
--94eb2c05be56259d3305340f0022--