linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonino Daplas <adaplas@pol.net>
To: John Bradford <john@grabjohn.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	schottelius@wdt.de, thoffman@arnor.net,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Re: New logo code [CONFIG OPTIONS]
Date: 19 Feb 2003 05:58:04 +0800	[thread overview]
Message-ID: <1045605436.1233.14.camel@localhost.localdomain> (raw)
In-Reply-To: <200302171932.h1HJWuiY011149@darkstar.example.net>

On Tue, 2003-02-18 at 03:32, John Bradford wrote:
> > 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?
> 

Possibly, it depends on the console/input developers if they want to add
something like fb_flash_logo() besides doing a kd_mksound(). Also, if
you don't mind compiling in a bunch of logo images to your kernel.

On a more practical note, the "scissors test" (I should have named this
"exclusive clipping test") can perhaps be enabled arbitrarily by
userland clients.  You'll be left with a rectangular screen space that
will not be touched by the console.  Then a distributor can do whatever
it wants with that screen estate, say an animating splash or a pop-up
window, which in theory can be triggered any time.

Tony




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2003-02-18 21:57 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
2003-02-18 21:58             ` Antonino Daplas [this message]

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=1045605436.1233.14.camel@localhost.localdomain \
    --to=adaplas@pol.net \
    --cc=geert@linux-m68k.org \
    --cc=john@grabjohn.com \
    --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).