9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] strange behaviour of igfx and vesa
Date: Wed, 22 Jun 2016 09:26:33 +0200	[thread overview]
Message-ID: <d3434e8516ba1b2240a2e0da6489bad7@felloff.net> (raw)
In-Reply-To: <f27b74bf681847c960fbea3946efdf4c@titan.jitaku.localdomain>

very good. the gmbus stuff is for reading edid. if aux/vga -p prints the
edid, then this probably not the issue. but you are on the right track.

the theory is that igfx programs the registers right that it knows
about (check the load function), otherwise you wouldnt see a picture
at all. (igfx disables all the ports and then reprograms everything).
so the missing bits might not even be in the driver.

we'r looking for the needle in the haystack. if you have a clean bios
trace, then you can use the power of text processing and make a list
of all the wport mmio addresses for both igfx and bios. that way, you
can find registers that the igfx driver doesnt know about but are
programmed by the bios. then we can look them up in the intel docs
and figure out what they do :-)

good luck!

--
cinap


  reply	other threads:[~2016-06-22  7:26 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 [this message]
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=d3434e8516ba1b2240a2e0da6489bad7@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).