From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] strange behaviour of igfx and vesa
Date: Thu, 30 Jun 2016 11:06:43 +0900 [thread overview]
Message-ID: <8b9fd1a4756cfaaff7fa02d2af2bc884@titan.jitaku.localdomain> (raw)
In-Reply-To: <b85b77331b39089ca4a69e997adca5c6@vaioL.jitaku.localdomain>
> I'm still experimenting this, but no success.
I think I did all I can do now, but not success.
Then, I'll post my results here for memory of someone else.
I added codes below to ensure the VBLANK timing to enable
Analog Display port according to the manual, like:
in load() function of igfx.c
------- from here-----
/* program ports */
if(igfx->pci->did == 0x29a2){ /* K.Okamoto */
igfx->adpa.v |= 1<<31; /* enable adpa */
wr(igfx, igfx->adpa.a, igfx->adpa.v);
igfx->adpa.v |= 3<<10; /* disable hsync/vsync */
wr(igfx, igfx->adpa.a, igfx->adpa.v);
wr(igfx, 0x070024, 0x207);
while((rr(igfx, 0x070024) & 1<<9) == 0)
{/* wait for VSYNC */
}
wr(igfx, 0x070024, 0x207);
while((rr(igfx, 0x070024) & 1<<9) == 0)
{/* wait for VSYNC */
}
}
igfx->adpa.v &= ~(3<<10); /* Monitor DPMS: on */
------to here-------
After somewhat longer period to wait the panel shouws no signal,
this fails to show screen.
Here, I got 0x207 or 0x4 etc on 0x70024 register after the wait loop,
which means above loops work right.
Next, I compared the two dump.rc (using mmio.all), one of which
is done after vesa --> aux/vga -m igfx -l 1680x1050x32
(this case works fine), and the other is done after boot the
terminal without aux/vga. Then, on the CGA console, I did the comand,
aux/vga -m igfx -l 1680x1050x32; dump.rc | pretty.rc >regdump.
The two register outputs were all the same without one value of
rmmio 00070000, which is not important here.
Therefore, I concluded the difference comes from neither the
settings of registers nor VSYNC problem.
Therefore, there should be something not written in the manual.
I can use this terminal by booting vesa mode, then
aux/vga -m igfx -l 1680x1050x32, which may be OK now.
Kenji
prev parent reply other threads:[~2016-06-30 2:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 6:48 kokamoto
2016-06-17 12:46 ` [9front] " cinap_lenrek
2016-06-17 23:40 ` kokamoto
2016-06-18 1:29 ` kokamoto
2016-06-18 7:45 ` kokamoto
2016-06-18 23:38 ` kokamoto
2016-06-19 5:58 ` kokamoto
2016-06-20 2:48 ` kokamoto
2016-06-20 4:14 ` kokamoto
2016-06-22 0:25 ` kokamoto
2016-06-22 7:26 ` cinap_lenrek
2016-06-23 6:43 ` kokamoto
2016-06-23 10:55 ` cinap_lenrek
2016-06-23 11:24 ` kokamoto
2016-06-25 1:50 ` kokamoto
2016-06-30 2:06 ` kokamoto [this message]
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=8b9fd1a4756cfaaff7fa02d2af2bc884@titan.jitaku.localdomain \
--to=kokamoto@hera.eonet.ne.jp \
--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).