From: Nico Schottelius <schottelius@wdt.de>
To: Torrey Hoffman <thoffman@arnor.net>
Cc: linux-fbdev-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] Re: New logo code [CONFIG OPTIONS]
Date: Sat, 15 Feb 2003 16:31:55 +0100 [thread overview]
Message-ID: <20030215153154.GB469@schottelius.org> (raw)
In-Reply-To: <1044472678.1321.388.camel@rohan.arnor.net>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
[snipped out patch discussion]
I think if the patch and the features talked about are included in the
kernel we'll have (names are not correct)
CONFIG_LOGO=y/n
CONFIG_LOGO_XRES=128
CONFIG_LOGO_YRES=64
CONFIG_LOGO_BPP=8
CONFIG_LOGO_PATH="" # (/usr/src/linux/.../logo/tux.pnm)
CONFIG_LOGO_POS_X="left|center|right" # or absolute ?
CONFIG_LOGO_POS_Y="top|center|bottom" # like X windows +110,+200 ?
CONFIG_LOGO_BGCOL=#ef0000 # depends on bpp of framebuffer...
I think this would be enough for all and possible implementable for the
developers..or am I wrong ?
Greetings,
Nico
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-15 15:31 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 ` Nico Schottelius [this message]
2003-02-17 10:36 ` Re: New logo code [CONFIG OPTIONS] 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
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=20030215153154.GB469@schottelius.org \
--to=schottelius@wdt.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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).