From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mta01.eonet.ne.jp ([203.140.81.20]) by ur; Fri Jun 17 19:40:21 EDT 2016
Received: from titan.jitaku.localdomain (182-164-107-94f1.osk3.eonet.ne.jp [182.164.107.94])
	by mailmsa11.mozu.eo.k-opti.ad.jp  with ESMTP id u5HNeFWV004001
	for <9front@9front.org>; Sat, 18 Jun 2016 08:40:15 +0900
To: 9front@9front.org
Subject:  Re: [9front] strange behaviour of igfx and vesa
Date: Sat, 18 Jun 2016 08:40:14 +0900
From: kokamoto@hera.eonet.ne.jp
Message-ID: <f4691f4927c2d517b5d1b702fc9d0c9f@titan.jitaku.localdomain>
In-Reply-To: <644ef2b1069fabf217cddbfd75b14cae@felloff.net>
References: <644ef2b1069fabf217cddbfd75b14cae@felloff.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: lossless mobile GPU callback AJAX over SOAP STM hypervisor 

> state. the vesa bios might initialze registers that the igfx
> driver misses.
> 
> http://felloff.net/usr/cinap_lenrek/igdump.tar

I'll try this.

However, I have a memory of ducument that says somthing about
the value which you use port# of "2" like:
		switch(x){
		case PortVGA:
			vga->edid[x] = snarfgmedid(igfx, 2, 0x50);
			break;
in snarf() function. 

The document has a table which says individual chip has a different 
port number for a same PortVGA...
My memory goes bad these days, however, I think you can find it
from Intel's support site which was a short paged one.

I may be wrong, however, the behaviour suggests it, I suppose.

Kenji