From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mta01.eonet.ne.jp ([203.140.81.45]) by ur; Sat Aug  6 08:55:52 EDT 2016
Received: from titan.jitaku.localdomain (101-141-38-118f1.osk3.eonet.ne.jp [101.141.38.118])
	by mailmsa12.mozu.eo.k-opti.ad.jp  with ESMTP id u76CtkpU012854
	for <9front@9front.org>; Sat, 6 Aug 2016 21:55:46 +0900
To: 9front@9front.org
Subject:  Re: [9front] core-i5(TypeSNB) and vesa mode
Date: Sat, 6 Aug 2016 21:55:46 +0900
From: kokamoto@hera.eonet.ne.jp
Message-ID: <2c1c64ff26d76f0bad2bbc3016e76534@titan.jitaku.localdomain>
In-Reply-To: <e6eba27d5f5cd3819f8874e3d6ac6020@titan.jitaku.localdomain>
References: <e7d9b3c909d55e83577563603ab1c499@felloff.net>
	<d917f0416c65913d9ba456d0c6353b13@titan.jitaku.localdomain>
	<e6eba27d5f5cd3819f8874e3d6ac6020@titan.jitaku.localdomain>
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: just-in-time HTTP over ORM wrapper-oriented markup 

> I think I got the reason.
> in snarfpipe()
> codes looks like:
> 	if(igfx->type == TypeIVB || igfx->type == TypeSNB) {
> 		p->fdi->txctl = snarfreg(igfx, o + 0x100);
> 
> 		o = 0xE0000 | x*0x1000;
> 		snarftrans(igfx, p->fdi, o);
> 
> 		p->fdi->dpctl = snarfreg(igfx, o + 0x300);	<===
> 
> Here, as our SandyBridge has two pipes, the value of p->fdi->dpctl could
> be snarfed only for dp[0] and dp[1], because snarfpipe()'x is the value of
> pipe, here 0 or 1.
> However, in my case, this machine is connected to DP[2], Displayport C.

No, it's wrong!

However, I have no message from this line in init():
	case PortDPA:
	case PortDPB:
	case PortDPC:
	case PortDPD:
		r = &igfx->dp[port - PortDPA].ctl;


print("dp[%d] ctl address = %ullx\n", (port-PortDPA), r->a);  <====

		if(r->a == 0)
			goto Badport;
		/* port enable */

Kenji