From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] More about /dev/draw
Date: Sun, 29 May 2016 13:58:21 +0100 [thread overview]
Message-ID: <CAOw7k5iZ+pTprCQj3CXybhsowtCzuLNwr3MD-Us+=w+Ni4RMgg@mail.gmail.com> (raw)
In-Reply-To: <CAG2UyHrmkS_OTT8Oj5wBvCgZg_F74S_H4uCXjzSDB8DnPJ7fig@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
On 29 May 2016 at 13:44, Dave MacFarlane <driusan@gmail.com> wrote:
> Why would the alpha channel work differently with the same image from the
> same code with the same hardware
> depending on the driver?
>
Because there might be a difference in the way the components inside the
pixel word are being interpreted or used by memdraw.
[-- Attachment #2: Type: text/html, Size: 650 bytes --]
next prev parent reply other threads:[~2016-05-29 12:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 17:23 Dave MacFarlane
2016-05-28 17:34 ` Skip Tavakkolian
2016-05-28 17:49 ` Dave MacFarlane
2016-05-28 18:04 ` hiro
2016-05-28 18:28 ` Steve Simon
2016-05-29 5:40 ` jfmxl
2016-05-29 5:50 ` Steve Simon
2016-05-29 5:59 ` jfmxl
2016-05-29 6:19 ` jfmxl
2016-05-29 8:05 ` hiro
2016-05-29 17:25 ` trebol55555
2016-05-31 8:41 ` Richard Miller
2016-05-31 8:14 ` Richard Miller
2016-05-31 14:18 ` jfmxl
2016-05-29 10:50 ` Charles Forsyth
2016-05-29 12:44 ` Dave MacFarlane
2016-05-29 12:58 ` Charles Forsyth [this message]
2016-05-30 0:30 ` Dave MacFarlane
2016-05-30 9:20 ` Richard Miller
2016-05-30 9:27 ` cinap_lenrek
2016-05-30 13:11 ` Dave MacFarlane
2016-05-30 10:08 ` Richard Miller
2016-05-30 12:37 ` Richard Miller
2016-05-30 13:13 ` Dave MacFarlane
2016-05-30 13:53 ` Richard Miller
[not found] <1927218855.974253.1464549855538.JavaMail.yahoo.ref@mail.yahoo.com>
2016-05-29 19:24 ` Brian L. Stuart
2016-05-29 22:47 ` jfmxl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOw7k5iZ+pTprCQj3CXybhsowtCzuLNwr3MD-Us+=w+Ni4RMgg@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).