All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Suchanek <hramrach@centrum.cz>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Antialiased fonts patch.
Date: Thu, 11 Feb 2010 14:30:59 +0100	[thread overview]
Message-ID: <a5d587fb1002110530h377d8de7sab7ec1b22de07be4@mail.gmail.com> (raw)
In-Reply-To: <1264500247.3195.22.camel@EK>

On 26 January 2010 11:04, Evgeny Kolesnikov <evgenyz@gmail.com> wrote:
> Hi,
>
>> At first I was completely against antialiasing support because of
>> performance impact. But it being optional decreases the later. However
>> there is one problem: your patch relies on text_layer to be RGBA8888
>> which was a mistake. RGBA8888 for text layer is vastly inefficient
>> especially on 16-bit framebuffer and CPUs with small cache. I had plans
>> to switch it to indexed color. Do you really need 8bits and 4 aren't
>> enough?
>
> I use 8-bit in order to give GRUB ability to look and feel exactly
> as other parts of OS, so yes, 8 bits are required. If one can't allow

Grub will never look and feel exactly as the OS unless you import
GTK/QT, its themes, freetype, ...

> this for his system - he can use 1-bit fonts. I don't really care about
> such situation just because other parts of desktop on such a system will
> be awful too.

In fact I think that 4bit antialiasing should suffice. 16 tones of the
same color should be more than enough for most cases. Still I am not
sure that it will make the rendering really faster than 8bit AA.

Only testing on various  real hardware can possibly answer the
question if and when one of the methods is faster. I would even expect
that none is overall faster and that system exist where either is.

Thanks

Michal



  parent reply	other threads:[~2010-02-11 13:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 13:19 grub-mkfont and DejaVu font problems Evgeny K
2010-01-21 13:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-22 11:46   ` Antialiased fonts patch Evgeny Kolesnikov
2010-01-22 12:53     ` BVK Chaitanya
2010-01-22 13:22       ` Evgeny Kolesnikov
2010-01-26  9:11     ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-26 10:04       ` Evgeny Kolesnikov
2010-01-26 11:59         ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-26 19:44           ` Carles Pina i Estany
2010-02-11  2:58         ` Vladimir 'φ-coder/phcoder' Serbinenko
     [not found]           ` <1265957146.2292.11.camel@EK>
2010-02-12  9:50             ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-11 13:30         ` Michal Suchanek [this message]
2010-02-12  6:21           ` richardvoigt
2010-02-12  6:48             ` Evgeny Kolesnikov
2010-02-12  7:08           ` Evgeny Kolesnikov
2010-02-12  7:20             ` Bruce Dubbs
2010-02-12  7:52               ` Evgeny Kolesnikov
2010-02-12  9:15               ` Michal Suchanek
2010-02-12  9:55               ` Vladimir 'φ-coder/phcoder' Serbinenko

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=a5d587fb1002110530h377d8de7sab7ec1b22de07be4@mail.gmail.com \
    --to=hramrach@centrum.cz \
    --cc=grub-devel@gnu.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.