From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] strange behaviour of igfx and vesa
Date: Fri, 17 Jun 2016 14:46:50 +0200 [thread overview]
Message-ID: <644ef2b1069fabf217cddbfd75b14cae@felloff.net> (raw)
In-Reply-To: <9964dda00ad1dae2d73742d1c7878f2b@mars.jitaku.localdomain>
state. the vesa bios might initialze registers that the igfx
driver misses.
"blank screen" doesnt say much. do you get a stable, but
black screen? or does the screen not even turn on? is the
backlight just off?
you can dump the register contents with aux/vga and compare
native igfx vs vesa + igfx.
this will only catch register differences that igfx knows
about tho.
it is possible to run realemu in trace mode (-p) and log all
the io reads and writes while vesa programs the card. then
sort thru the log to identify registers that the driver doesnt
know about.
i'v written some scripts to decode realemu bios traces that
you could adapt for your card:
http://felloff.net/usr/cinap_lenrek/igdump.tar
you certanly have to change the port offsets for the banked
address/data register in mmio.awk (check the io bar of
the graphics card of your system)
in any case, make a realemu trace (from the initial no-graphics
state). so we get a real detailed programming sequence for the
card that is known to work. once we have that, it is possibe
to figure out what we are missing or where igfx diverges.
dont run the realemu trace when grapics is already running.
because vesa might skip initialization of registers that have
already been programmed, so you'll not catch the missing bits.
--
cinap
next prev parent reply other threads:[~2016-06-17 12:46 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 ` cinap_lenrek [this message]
2016-06-17 23:40 ` [9front] " 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
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=644ef2b1069fabf217cddbfd75b14cae@felloff.net \
--to=cinap_lenrek@felloff.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).