[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Improve handling of "keep" in gfxpayload

From: Robert Millan
Subject: Re: [PATCH] Improve handling of "keep" in gfxpayload
Date: Mon, 10 Aug 2009 17:27:25 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Mon, Aug 10, 2009 at 02:05:15PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> What is the linux behaviour with 0x0F04? Does it just keep the mode?
> What if the same mode is passed as a value? Does linux redoes the
> modesetting? If 0x0F04 works ok I would prefer to always pass it when
> kernel is booted in graphical mode. VESA mode numbers are an artifact
> and when grub2 has its own graphical drivers it won't correspond to
> anything.

I might be missing something, but AFAICT VESA mode numbers are only passed
by the user in the "vga=" option.

There's also the `vid_mode' parameter in Linux header, but it's only used by
legacy code, and with the 32-bit boot protocol Linux doesn't read it.

Does 0x0F04 really do something when used in combination with Linux' vesafb?

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 via email to

[Prev in Thread] Current Thread [Next in Thread]