All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
	Linux Frame Buffer Device Development 
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Penguin logos
Date: Mon, 12 Mar 2001 07:43:21 +0100	[thread overview]
Message-ID: <3AAC7009.BFA260CD@evision-ventures.com> (raw)
In-Reply-To: <200103120112.f2C1Csj165543@saturn.cs.uml.edu>

"Albert D. Cahalan" wrote:
> 
> Geert Uytterhoeven writes:
> 
> >   - The colors for the 16 color logo are wrong. We used a hack to
> >     give the logo its own color palette, but this no longer works
> >     as a side effect of a console color map bug being fixed a while
> >     ago. The solution is to replace the logo with a new one that
> >     uses the standard VGA console palette.
> 
> Good idea, but the feet don't look too good. Either dither a bit,
> or pick a single color for the feet. Maybe a checkerboard-dither
> would get close to the right color without looking grainy.
> 
> >   - There are still some politically-incorrect (PI) logos of a penguin
> >     holding a glass of beer or wine (or perhaps even worse? :-).
> 
> Those also just look bad. The drink sort of floats above the penguin's
> foot. It really looks like it was just pasted onto the image.
> 
> The arch-specific logos look bad in general, and the swirly gray
> background isn't so great either. Why not use the original image?

I agree fully about the swirly gray - it's just looks ugly chlidish,
dilletantic
and very tasteless... plain color or some gui alike border would look
much better.

> 
> > Changes:
> >  1. Update the frame buffer console code to no longer change the
> >     palette when displaying the 16 color logo. Remove the tricks
> >     to load the logo palette in unused palette entries on displays
> >     with >= 32 colors.
> 
> I used to have only 256 colors on my display. I upgraded because
> there still isn't a global system palette. I'd have been happy
> enough with 256 colors allocated in a sane way, for kernel & X:
> 
> 1. the 16 VGA colors and extra 4 Windows colors (so Wine can work)
> 2. the 216 Netscape colors
> 3. gray: 0x00, 0x11, 0x22... 0xff, plus both 0x7f and 0x80
> 4. everything else reserved for future global allocation
> 
> The current situation is way too painful to use.

  reply	other threads:[~2001-03-12  5:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-08 20:12 [PATCH] Penguin logos Geert Uytterhoeven
2001-03-08 22:28 ` Oliver Xymoron
2001-03-12  1:12 ` Albert D. Cahalan
2001-03-12  6:43   ` Martin Dalecki [this message]
2001-05-03 20:16 ` Geert Uytterhoeven
2001-05-04  8:44   ` [Linux-fbdev-devel] " Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2001-03-08 21:30 Simon Richter

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=3AAC7009.BFA260CD@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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.