From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH 1/2] Replace hook-based with flag-based approach for choosing video mode
Date: Mon, 24 Aug 2009 00:36:20 +0200 [thread overview]
Message-ID: <20090823223620.GA25769@thorin> (raw)
In-Reply-To: <d7ead6de0908230358t67bdd20dj755c4a49f8ca248f@mail.gmail.com>
On Sun, Aug 23, 2009 at 12:58:46PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> > Btw, please include a ChangeLog entry next time.
> Ok. I will from now one but it will also mean a delay sending patches ;)
I know it's a PITA, but consider that it needs to be done anyway. When you
think about that, it's not so bad :-)
> > People usually associate "pure text" mode with a managed mode like 80x25
> > vga text. I understand here it means something else,
> It means exactly the modes like 80x25
Then I don't understand what
grub_video_set_mode ("1024x768;800x600;640x480", GRUB_VIDEO_MODE_TYPE_PURE_TEXT)
could mean. Are you requesting a graphical mode or a text one? If it's a
text one, why the list of resolutions?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-08-23 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 18:51 [PATCH 1/2] Replace hook-based with flag-based approach for choosing video mode Vladimir 'phcoder' Serbinenko
2009-08-17 13:51 ` Robert Millan
2009-08-21 12:54 ` Vladimir 'phcoder' Serbinenko
2009-08-23 10:25 ` Robert Millan
2009-08-23 10:30 ` Robert Millan
2009-08-23 10:58 ` Vladimir 'phcoder' Serbinenko
2009-08-23 22:36 ` Robert Millan [this message]
2009-08-23 22:40 ` Vladimir '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=20090823223620.GA25769@thorin \
--to=rmh@aybabtu.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.