From: David Odin <David.Odin@bigfoot.com>
To: "Kevin Ilchmann Jørgensen" <kij@odense.kollegienet.dk>
Cc: Linux Kernel <linux-kernel@vger.rutgers.edu>
Subject: Re: Format of linux_logo.h
Date: Sun, 31 Oct 1999 01:09:31 +0200 [thread overview]
Message-ID: <19991031010930.A23564@bigfoot.com> (raw)
In-Reply-To: =?iso-8859-1?Q?=3CPine=2ELNX=2E4=2E20=2E9910310019270=2E9892-100000=40be?= =?iso-8859-1?Q?rta=2Elocal104=3E=3B_from_Kevin_Ilchmann_J=F8rgensen_on_S?= =?iso-8859-1?Q?un=2C_Oct_31=2C_1999_at_12:30:20AM_+0200?=
[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]
On Sun, Oct 31, 1999 at 12:30:20AM +0200, Kevin Ilchmann Jørgensen wrote:
> Hi there,
>
> We want to put our own boot_logo in the kernel, when framebuffers is
> enabled. But the format seems a little spectacular. All of our graphical
> manipulation programs (ee, xv, gimp) can save the real format, but only
> B/W (.xbm). Anyone has a script or a link to another program that does the
> job?
>
> Or even better; a link to an URL that tells about boot logo with
> framebuffers enabled - the format's etc.?
>
I remember that there is a Gimp-plugin in the plugin registry that save an
image in the bootlogo.h format. I can't remember its name though.
Here are some specs of the logo:
It should be 80x80 pix, with less than 224 colors...
The logo itself it composed of four array of unsigned char
The first three are color lookup tables for the red, green, and blue.
- linux_logo_red[] contains the quantity of red for each color index of the
logo.
- same for green and blue.
- linux_logo[] contains 3*80*80 bytes. Each triplet of bytes represent a
pixel. These bytes are indexes in the red, green and blue
tables to use with the previous tables.
You'll find attached a package with some logos and a tools to show them
on the screen (you'll need gtk to compile it). By looking in it, you should
be able to write your own loading/saving routines.
Regards,
DindinX
--
David.Odin@bigfoot.com
The day-to-day travails of the IBM programmer are so amusing to most of
us who are fortunate enough never to have been one -- like watching
Charlie Chaplin trying to cook a shoe.
[-- Attachment #2: logo.tar.gz --]
[-- Type: application/x-tar-gz, Size: 34992 bytes --]
parent reply other threads:[~1999-10-30 23:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.20.9910310019270.9892-100000@berta.local104>]
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=19991031010930.A23564@bigfoot.com \
--to=david.odin@bigfoot.com \
--cc=kij@odense.kollegienet.dk \
--cc=linux-kernel@vger.rutgers.edu \
/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
all inboxes | Powered by JetHome®