From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] what change of vesa...
Date: Fri, 05 Jun 2015 05:47:54 +0000 [thread overview]
Message-ID: <20150605054754.Horde.4Y3PRthjsf82m18ff_jAZbs@ssl.eumx.net> (raw)
In-Reply-To: <59CBA0461FDA4C33A403BE5428B85959@jitaku.localdomain>
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
next prev parent reply other threads:[~2015-06-05 5:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 5:43 Kenji Okamoto
2015-06-05 5:47 ` Kurt H Maier [this message]
2015-06-07 20:49 ` [9front] " cinap_lenrek
2015-06-08 0:21 ` Kenji Okamoto
2015-06-07 15:34 ` kokamoto
2015-06-08 0:43 ` cinap_lenrek
2015-06-08 0:30 ` cinap_lenrek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150605054754.Horde.4Y3PRthjsf82m18ff_jAZbs@ssl.eumx.net \
--to=khm@sciops.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).