All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeny Kolesnikov <evgenyz@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Antialiased fonts patch.
Date: Tue, 26 Jan 2010 16:04:07 +0600	[thread overview]
Message-ID: <1264500247.3195.22.camel@EK> (raw)
In-Reply-To: <4B5EB1A5.5040200@gmail.com>

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
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.

> If 4 are enough we could make text_layer IA44 (indexed-4 bits,
> alpha 4 bits) if you need 8 bits we can do IA88. I'm not sure which one
> is faster: firs one is more cache-efficient, second one requires less
> ALU. Are you interested in implementing this?

Actually I'm planning to add 32-bit AA (heh-heh). Sub-pixel AA for LCD
monitors for complete match with xorg capabilities. And this just can't
be done in indexed mode.

So I can suggest to make division: 1-bit & indexed text layer vs
8(32)-bit & RGBA layer. First is for speed, second (and third) 
is for beauty (BURG project is already interested in - Bean, help
me :)). Doing it half-way will be nor fast nor appealing.

And yes, I'm interested in doing it in most effective way: blitter,
optimizations etc., just give me the direction.

> > Everything my path does is:
> >
> > 1) Enriches grub-mkfont with ability to write (and debug with -vv) 
> > pff3 (as I call it now) font format. There are 2 differences between
> > pff2 and pff3 formats: FILE magic (PFF2 becomes PFF3) and DATA block
> > entires size multiples by 8 (1bit -> 8bit). In other words PFF3 stores
> > 8-bit alpha channel instead of 1-bit.
> > And grub-mkfont will still be able to generate pff2, of course.
> >
> >   
> And by default grub-mkfont should generate not antialiased font for
> performance reasons. But user or theme creator can choose to use
> antialiased fonts if they wish.

It's exactly the way my patch does it. AA is optional and used
explicitly.





  reply	other threads:[~2010-01-26 10:04 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 [this message]
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
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=1264500247.3195.22.camel@EK \
    --to=evgenyz@gmail.com \
    --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.