From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] strange behaviour of igfx and vesa
Date: Sat, 25 Jun 2016 10:50:08 +0900 [thread overview]
Message-ID: <b85b77331b39089ca4a69e997adca5c6@vaioL.jitaku.localdomain> (raw)
In-Reply-To: <442327564c1e2a2bf938a6828dc348e6@titan.jitaku.localdomain>
I'm still experimenting this, but no success.
When I posted last mail, and pointed supposed to do some large
rewriting neccessary, which was thought less.
At that time, I was thinking to change in init() function for 29a2 chip.
Now I fugured it was wrong, and am now adding some code in load()
function.
Now experimenting codes are(in load() function):
/* program vga plane */
loadreg(igfx, igfx->vgacntrl);
/* program ports */
/* from here====K.Okamoto====*/
if(igfx->pci->did == 0x29a2){ /* K.Okamoto */
wr(igfx, igfx->adpa.a, 1<<31); /* enable adpa */
wr(igfx, igfx->adpa.a, 3<<10); /* off disable hsync/vsync */
wr(igfx, igfx->adpa.a, 1<<15); /* use 4,3 bits for hsync/vsync */
// wr(igfx, 0x070024, 1<<9);
// while((rr(igfx, 0x070024) & 1<<9) == 0)
// continue;
// wr(igfx, 0x070024, 1<<1);
// wr(igfx, 0x070024, 1<<9);
wr(igfx, 0x070024, 0x207);
while((rr(igfx, 0x070024) & 0x207) == 0)
continue;
wr(igfx, igfx->adpa.a, 1<<15); /* use VGA bits for hsync/vsync */
wr(igfx, igfx->adpa.a, ~(3<<10)); /* adpa hsync/vsynx on */
}
/* ======to here K.Okamoto======*/
loadreg(igfx, igfx->adpa);
igfx->adpa.v &= ~(3<<10); /* Monitor DPMS: on */
Results are not successfull, however, I suppose I'm now on right truck.
If you have some comments on this, please do it.
Kenji
next prev parent reply other threads:[~2016-06-25 1:50 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 [this message]
2016-06-30 2:06 ` kokamoto
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=b85b77331b39089ca4a69e997adca5c6@vaioL.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).