From: John Bradford <john@grabjohn.com>
To: Antonino Daplas <adaplas@pol.net>
Cc: geert@linux-m68k.org, schottelius@wdt.de, thoffman@arnor.net,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] Re: New logo code [CONFIG OPTIONS]
Date: Mon, 17 Feb 2003 19:32:56 +0000 (GMT) [thread overview]
Message-ID: <200302171932.h1HJWuiY011149@darkstar.example.net> (raw)
In-Reply-To: <1045509708.1209.22.camel@localhost.localdomain> from "Antonino Daplas" at Feb 18, 2003 03:23:11 AM
> So how about making the logo "float" above/obscure the text (ie,
> overlay)? It's not difficult to implement since fbcon.c has "redraw"
> versions of fbcon_bmove() and fbcon_clear(). All that needs to be done
> is do a "scissors" test before an fb_imageblit().
On the subject of the new logo code, would it be worth making it do
something, (change colour, move, or animate), during a console bell?
John.
next prev parent reply other threads:[~2003-02-17 19:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.21.0301281606580.9269-100000@vervain.sonytel.be>
2003-02-05 12:37 ` Re: New logo code (fwd) Geert Uytterhoeven
2003-02-05 7:14 ` [Linux-fbdev-devel] " Antonino Daplas
2003-02-06 9:19 ` Geert Uytterhoeven
2003-02-05 9:24 ` Antonino Daplas
2003-02-05 14:14 ` [Linux-fbdev-devel] " Christoph Hellwig
2003-02-12 20:37 ` James Simmons
2003-02-12 20:51 ` Geert Uytterhoeven
2003-02-13 9:38 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2003-03-05 19:53 ` James Simmons
2003-02-05 19:17 ` [Linux-fbdev-devel] " Torrey Hoffman
2003-02-05 7:15 ` Antonino Daplas
2003-02-06 9:22 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2003-02-15 15:31 ` [Linux-fbdev-devel] Re: New logo code [CONFIG OPTIONS] Nico Schottelius
2003-02-17 10:36 ` Geert Uytterhoeven
2003-02-17 19:23 ` [Linux-fbdev-devel] " Antonino Daplas
2003-02-17 19:32 ` John Bradford [this message]
2003-02-18 21:58 ` Antonino Daplas
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=200302171932.h1HJWuiY011149@darkstar.example.net \
--to=john@grabjohn.com \
--cc=adaplas@pol.net \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=schottelius@wdt.de \
--cc=thoffman@arnor.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).