From: Antonino Daplas <adaplas@pol.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: James Simmons <jsimmons@infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: [PATCH]: image.depth fix to accomodate monochrome cards
Date: 11 Jan 2003 21:47:18 +0800 [thread overview]
Message-ID: <1042292794.1389.91.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.21.0301111422040.18570-100000@vervain.sonytel.be>
On Sat, 2003-01-11 at 21:24, Geert Uytterhoeven wrote:
> >
> > Do you think this will work? The only problem I can think of is a color
> > expansion request where both bg and fg is 0.
>
> And that can happen, try <ESC>[31m<ESC>[41m to set both to red.
>
> > Or to totally eliminate the above possibility, add an extra field in
> > struct fb_image to denote color expansion vs logo drawing. Again, only
> > mono cards will need to do this test.
>
> Ugh, why invent a new field if we can use an existing field? depth == 0 is
> invalid for image blitting anyway.
>
No argument here.
Tony
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-11 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 16:16 [PATCH]: image.depth fix to accomodate monochrome cards Antonino Daplas
2003-01-07 21:06 ` Geert Uytterhoeven
2003-01-08 2:41 ` Antonino Daplas
2003-01-08 9:52 ` Geert Uytterhoeven
2003-01-08 16:25 ` Antonino Daplas
2003-01-08 16:51 ` Geert Uytterhoeven
2003-01-10 19:27 ` James Simmons
2003-01-10 19:43 ` Geert Uytterhoeven
2003-01-11 5:10 ` Antonino Daplas
2003-01-11 13:24 ` Geert Uytterhoeven
2003-01-11 13:47 ` Antonino Daplas [this message]
2003-02-05 15:03 ` Geert Uytterhoeven
2003-02-05 7:14 ` Antonino Daplas
2003-02-12 20:50 ` James Simmons
2003-02-12 23:37 ` Antonino Daplas
2003-02-13 9:27 ` Geert Uytterhoeven
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=1042292794.1389.91.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.