public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Zwane Mwaikambo <zwane@infradead.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@suse.de>, Tobias Hain <tobias.hain@gmx.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] Don't probe for DDC on VBE1.2
Date: Thu, 15 Feb 2007 20:56:58 -0800	[thread overview]
Message-ID: <20070215205658.56096f97.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702132145460.28458@montezuma.fsmlabs.com>

On Thu, 15 Feb 2007 08:29:49 -0800 (PST) Zwane Mwaikambo <zwane@infradead.org> wrote:

> VBE1.2 doesn't support function 15h (DDC) resulting in a 'hang' whilst
> uncompressing kernel with some video cards. Make sure we check VBE version 
> before fiddling around with DDC.
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=1458
> 
> Opened: 2003-10-30 09:12 Last update: 2007-02-13 22:03
> 
> :(
> 
> Much thanks to Tobias Hain for help in testing and investigating the bug. 
> Tested on;
> 
> i386, Chips & Technologies 65548 VESA VBE 1.2
> CONFIG_VIDEO_SELECT=Y
> CONFIG_FIRMWARE_EDID=Y
> 
> Untested on x86_64.
> 
> Signed-off-by: Zwane Mwaikambo <zwane@infradead.org>
> 
> Index: linux-2.6.20-rc6-mm1/arch/i386/boot/video.S
> ===================================================================
> RCS file: /home/cvsroot/linux-2.6.20-rc6-mm1/arch/i386/boot/video.S,v
> retrieving revision 1.1.1.1
> diff -u -p -B -r1.1.1.1 video.S
> --- linux-2.6.20-rc6-mm1/arch/i386/boot/video.S	30 Jan 2007 05:28:31 -0000	1.1.1.1
> +++ linux-2.6.20-rc6-mm1/arch/i386/boot/video.S	15 Feb 2007 16:27:32 -0000
> @@ -1945,6 +1945,20 @@ store_edid:
>  	rep
>  	stosl
>  
> +	pushw	%es
> +	pushw	%ds
> +	popw	%es
> +	leaw	modelist+1024, %di
> +	movw	$0x4f00, %ax
> +	int	$0x10
> +	popw	%es
> +
> +	cmpw	$0x004f, %ax
> +	jne	no_edid
> +
> +	cmpw	$0x0102, 4(%di)			# only do EDID on > 1.2
> +	je	no_edid
> +
>  	pushw   %es				# save ES
>  	xorw    %di, %di                        # Report Capability
>  	pushw   %di

This makes the long-suffering-but-vigorously-defended Vaio come up with a
black display.  Everything's working OK otherwise.  Sort of a Black Screen
of Life.  I wouldn't call it an improvement though.

  parent reply	other threads:[~2007-02-16  4:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-15 16:29 [PATCH] Don't probe for DDC on VBE1.2 Zwane Mwaikambo
2007-02-15 20:41 ` Randy Dunlap
2007-02-15 22:35   ` Zwane Mwaikambo
2007-02-16  4:56 ` Andrew Morton [this message]
2007-02-16  5:35   ` Zwane Mwaikambo
2007-02-16  5:45     ` Andrew Morton
2007-02-16  5:51       ` Andrew Morton
2007-02-16  5:59         ` Zwane Mwaikambo
2007-02-16  7:02           ` Andrew Morton
2007-02-16 14:39             ` Zwane Mwaikambo
2007-02-16 18:22               ` Andrew Morton
2007-02-17  8:35                 ` Zwane Mwaikambo
2007-02-17  8:49                   ` Andrew Morton
2007-02-18 18:57                   ` AW: " Tobias Hain
2007-02-18 21:53                   ` Andi Kleen
2007-02-19  0:37                     ` Zwane Mwaikambo
2007-02-19 10:37                       ` Andi Kleen
2007-02-19 12:32                         ` Zwane Mwaikambo

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=20070215205658.56096f97.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ak@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tobias.hain@gmx.de \
    --cc=zwane@infradead.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