From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Dave Jones <davej@redhat.com>, Yum Rayan <yum.rayan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] VBE DDC bios call stalls boot
Date: Mon, 24 Apr 2006 07:47:29 +0800 [thread overview]
Message-ID: <444C1211.8090505@gmail.com> (raw)
In-Reply-To: <20060423202428.GC14680@redhat.com>
Dave Jones wrote:
> On Sun, Apr 23, 2006 at 12:08:27PM -0700, Yum Rayan wrote:
>
> > There is a bios call to check if read EDID is supported. My first
> > thought was that before doing read EDID, video.S should first check to
> > see if the hardware supports the read EDID feature. Unfortunately that
> > bios call too ends up in the woods until I physically
> > disconnect/reconnect my CPU video output that feeds into the KVM.
>
> Is this how your patch looked when you tried this ?
I've discovered that checking for availability does not give any added benefit,
but this is the correct approach and I have to agree with this patch.
Tony
next prev parent reply other threads:[~2006-04-23 23:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 19:08 [RFC] VBE DDC bios call stalls boot Yum Rayan
2006-04-23 20:14 ` Ingo Oeser
2006-04-23 23:40 ` Antonino A. Daplas
2006-04-23 20:24 ` Dave Jones
2006-04-23 23:47 ` Antonino A. Daplas [this message]
2006-04-24 7:27 ` Yum Rayan
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=444C1211.8090505@gmail.com \
--to=adaplas@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yum.rayan@gmail.com \
/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