From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from owm.eumx.net ([91.82.101.43]) by pp; Fri Jun  5 01:48:01 EDT 2015
Date: Fri, 05 Jun 2015 05:47:54 +0000
Message-ID: <20150605054754.Horde.4Y3PRthjsf82m18ff_jAZbs@ssl.eumx.net>
List-ID: <9front.9front.org>
X-Glyph: ➈
X-Bullshit: virtual base ACPI component-aware template
From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] what change of vesa...
In-Reply-To: <59CBA0461FDA4C33A403BE5428B85959@jitaku.localdomain>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline

Quoting Kenji Okamoto <kokamoto@hera.eonet.ne.jp>:

> I crushed my 9front file server several months ago.
> I got fortunately motivation to reconstruct the system
> again these days, and got a recent CDROM (May 24, 2015).
>
> Now I have strange problem on my nvidia card, which say
> somethin strange handling..., which leads me to non rio.
> Then, I tried vesa mode with 1024x768x8 which runs fine.
>
> 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.
>
> Kenji

aux/vga: remove vbs/vbe from mode, use shs/ehs when sync is ment,  
prefer detailed timing in edid
http://code.9front.org/hg/plan9front/rev/d16d837b898c

aux/vga: use optional edid information to determine mode when vgadb fails
http://code.9front.org/hg/plan9front/rev/69d00d22733b

and you might want to look at aux/vga: cleanup vesa code
http://code.9front.org/hg/plan9front/rev/7ccbd823958c

wherein cinap talks about nvidiascale() -- not sure if it's related.

khm