From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mta01.eonet.ne.jp ([203.140.81.47]) by pp; Sun Jun  7 20:21:18 EDT 2015
Received: from neptune (101-140-104-248f1.osk3.eonet.ne.jp [101.140.104.248])
	by mailmsa12.mozu.eo.k-opti.ad.jp  with ESMTP id t580LCiN027248
	for <9front@9front.org>; Mon, 8 Jun 2015 09:21:12 +0900
Message-ID: <697F978772C44FA3B3A604D896E44F3D@jitaku.localdomain>
List-ID: <9front.9front.org>
X-Glyph: ➈
X-Bullshit: generic strategy
From: "Kenji Okamoto" <kokamoto@hera.eonet.ne.jp>
To: <9front@9front.org>
References: <90445d4090491ca8ef71805b109ea8d4@felloff.net>
In-Reply-To: <90445d4090491ca8ef71805b109ea8d4@felloff.net>
Subject: Re: [9front] what change of vesa...
Date: Mon, 8 Jun 2015 09:21:12 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3528.331
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3528.331

Thanks cinap.
Yes, it solved the problem.

Sorry my delay of response.
I was out of email these two days.

Kenji
-----Original Message----- 
From: cinap_lenrek@felloff.net 
Sent: Monday, June 08, 2015 5:49 AM 
To: 9front@9front.org 
Subject: Re: [9front] what change of vesa... 

> What were the changes on this vesa related timing things
> cinap reported before.   Can I see the difference of old and
> new codes.   As I mentioned above, I crushed my file server,
> and cannot see them by myself.

vesa shouldnt be affected by that at all. the timings are required
for native drivers. what went in new is that nvidiascale stuff,
maybe that screws up on your card. have you tried commenting it
out?

--
cinap