All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Video mode fixes in linux loader
Date: Wed, 13 May 2009 22:47:19 +0200	[thread overview]
Message-ID: <20090513204719.GA12098@thorin> (raw)
In-Reply-To: <49FF652F.2070703@earthlink.net>

On Mon, May 04, 2009 at 05:59:11PM -0400, BandiPat wrote:
> Robert Millan wrote:
>> Btw, I increased the mode list considerably (using documented modes from
>> Wikipedia).  Chances that your ultra-weird mode of choice is supported are
>> much greater now.
>>
>> There's still no fuzzy matching, though.  I'm not sure if we'd want to do
>> that at all for vga= modes, since we already do it properly in our video
>> subsystem.
>>
> =========
> I'll give them a look as soon as I can get something new built.  I'll  
> have to admit, I didn't expect you guys to go to so much trouble, since  
> the vga= will be going away anyhow.  We can all live with the "fuzzy  
> matching" for now, until you get the new video subsystem operating  
> properly.  Don't put a lot of time into something that won't be used  
> much longer, as we can live with things as they are for the moment.

Maybe you're right :-/

Hopefuly this will be less of a problem when we can set it from a variable
using a sane interface...

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



  reply	other threads:[~2009-05-13 20:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 15:34 [PATCH] Video mode fixes in linux loader Pavel Roskin
2009-04-07  0:31 ` Yoshinori K. Okuji
2009-04-07  0:49   ` Pavel Roskin
2009-04-07  7:31     ` phcoder
2009-04-07 22:04       ` Pavel Roskin
2009-04-12 19:11         ` phcoder
2009-04-12 20:43           ` Pavel Roskin
2009-04-13 14:16 ` Robert Millan
2009-04-13 14:45   ` Robert Millan
2009-04-13 15:41     ` Pavel Roskin
2009-04-13 19:05       ` Robert Millan
2009-04-13 23:20         ` Pavel Roskin
2009-04-14  0:02           ` phcoder
2009-05-02 11:38             ` Robert Millan
2009-05-02 11:31           ` Robert Millan
2009-05-02 15:32             ` Robert Millan
2009-05-03  0:03               ` BandiPat
2009-05-03 15:53                 ` Robert Millan
2009-05-04 15:15                   ` BandiPat
2009-05-04 16:01                     ` Robert Millan
2009-05-04 18:16                       ` BandiPat
2009-05-04 18:16                         ` Felix Zielcke
2009-05-04 20:30                   ` Robert Millan
2009-05-04 21:59                     ` BandiPat
2009-05-13 20:47                       ` Robert Millan [this message]
2009-05-04 18:04               ` Robert Millan
2009-05-03 13:18             ` Isaac Dupree
2009-05-03 15:50               ` Robert Millan
2009-04-13 15:16   ` Pavel Roskin
2009-04-13 18:59     ` Robert Millan

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=20090513204719.GA12098@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.