From: Dave Jones <davej@redhat.com>
To: Yum Rayan <yum.rayan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] VBE DDC bios call stalls boot
Date: Sun, 23 Apr 2006 16:24:28 -0400 [thread overview]
Message-ID: <20060423202428.GC14680@redhat.com> (raw)
In-Reply-To: <df35dfeb0604231208x416b7ab0ya612d918bb239140@mail.gmail.com>
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 ?
Dave
--- linux-2.6.15/arch/i386/boot/video.S~ 2006-01-06 01:26:06.000000000 -0500
+++ linux-2.6.15/arch/i386/boot/video.S 2006-01-06 01:28:40.000000000 -0500
@@ -1951,9 +1951,18 @@ store_edid:
stosl
movw $0x4f15, %ax # do VBE/DDC
- movw $0x01, %bx
+ movw $0x00, %bx # INSTALLATION CHECK / CAPABILITIES
movw $0x00, %cx
- movw $0x00, %dx
+ movw $0x00, %dx
+ movw $0x140, %di
+ int $0x10
+ cmpb $0x01, %ah
+ je no_edid
+
+ movw $0x4f15, %ax # do VBE/DDC
+ movw $0x01, %bx # READ_EDID
+ movw $0x00, %cx
+ movw $0x00, %dx
movw $0x140, %di
int $0x10
--- linux-2.6.15/arch/i386/boot/video.S~ 2006-01-06 02:55:20.000000000 -0500
+++ linux-2.6.15/arch/i386/boot/video.S 2006-01-06 02:55:28.000000000 -0500
@@ -1966,6 +1966,7 @@ store_edid:
movw $0x140, %di
int $0x10
+no_edid:
popw %di # restore all registers
popw %dx
popw %cx
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-04-23 20:24 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 [this message]
2006-04-23 23:47 ` Antonino A. Daplas
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=20060423202428.GC14680@redhat.com \
--to=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 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.