All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub_func_test (video checksums tests)
Date: Sun, 7 Dec 2014 20:00:21 +0300	[thread overview]
Message-ID: <20141207200021.28fa94a3@opensuse.site> (raw)
In-Reply-To: <5484811C.9040707@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

В Sun, 07 Dec 2014 17:32:28 +0100
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:

> On 05.12.2014 16:33, Andrei Borzenkov wrote:
> > If I understand it correctly, it computes checksums of each frame on
> > gfxterm. But will not screen content depend on QEMU version, font
> > source used to create unifont and probably other? I.e. - how useful is
> > it to be included in distribution?
> > 
> It doesn't depend on qemu version. But unfortunately it depends on the
> font. Can we somehow pin the font used?

It does use unifont, but probably different version. I have

Name        : gnu-unifont-bitmap-fonts
Version     : 20080123

The only way to make sure is probably to ship unifont as part of grub
if possible.

> > I ask because it fails for me and I'm not sure whether it's worth to
> > refresh checksums.h or simply ignore it. 
> > 
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > https://lists.gnu.org/mailman/listinfo/grub-devel
> > 
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2014-12-07 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 15:33 grub_func_test (video checksums tests) Andrei Borzenkov
2014-12-07 16:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-12-07 17:00   ` Andrei Borzenkov [this message]

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=20141207200021.28fa94a3@opensuse.site \
    --to=arvidjaar@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.