From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mta01.eonet.ne.jp ([203.140.81.45]) by ur; Fri Jul 29 07:42:37 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 u6TBgUnL013109
	for <9front@9front.org>; Fri, 29 Jul 2016 20:42:30 +0900
To: 9front@9front.org
Subject:  Re: [9front] core-i5(TypeSNB) and vesa mode
Date: Fri, 29 Jul 2016 20:42:30 +0900
From: kokamoto@hera.eonet.ne.jp
Message-ID: <21c8a94eda4722cc4af1cf1435bd3921@titan.jitaku.localdomain>
In-Reply-To: <76b3c084c8350c0ae67cfcaaebe8d122@felloff.net>
References: <76b3c084c8350c0ae67cfcaaebe8d122@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: overflow-preventing factory HTTP over SVG interface-scale component-oriented enhancement-aware solution 

> how do you know the freqency is the issue? 

The screen sitting more right hand side, but not all.
I can see the shape of mouse or opened rio terminal window etc,
but cannot read the character.  Such shiftness or line by line
dislocation seems like be explained by the difference of the
fitted frequency.   Probably, the m, n values are not good.

>you could setup
> that screen with vesa and then snarf the registers and see
> what it programs into the dpll regs.

AS I said before, the vesa bios of this machine works only for
Displayport.

Kenji