public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86-boot: don't request VBE2 information
Date: Thu, 06 Mar 2008 17:16:52 +0100	[thread overview]
Message-ID: <87skz3g74b.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <47D00AC0.8010805@zytor.com> (H. Peter Anvin's message of "Thu\, 06 Mar 2008 07\:16\:16 -0800")

>>>>> "H" == H Peter Anvin <hpa@zytor.com> writes:

 >> Disassembing the video BIOS shows that it overflows the vesa_general_info
 >> structure when VBE2 data is requested because the source addresses for the
 >> information strings which get strcpy'ed to the buffer lie outside the 32K
 >> BIOS code (and hence contain long sequences of 0xff's).
 >> 

 H> I'm slightly concerned about this, because we *do* use VBE2 data -
 H> just not the stuff that this particular BIOS seems to key on (and
 H> break.)

Well, we use the version info to know if we can request EDID data, but
otherwise I don't see any VBE2 stuff in vesa_general_info used.

A VBE2+ compatible BIOS should still put the correct version number in
the VBE info block even if you don't request VBE2 data (E.G. the
version gets set to 3.0 independently of VBE2 or not in the disasm I
sent).

 H> On the other hand, until we get an example on something that breaks
 H> with the change, we might as well try it, since we have an example on
 H> something that breaks with it.  We should monitor carefully, though.

Great. This was how the old asm version used to do it as well.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2008-03-06 16:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06  9:56 [PATCH] x86-boot: don't request VBE2 information Peter Korsgaard
2008-03-06 10:24 ` Ingo Molnar
2008-03-06 15:16 ` H. Peter Anvin
2008-03-06 16:16   ` Peter Korsgaard [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=87skz3g74b.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox