From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] strange behaviour of igfx and vesa
Date: Wed, 22 Jun 2016 09:25:21 +0900 [thread overview]
Message-ID: <f27b74bf681847c960fbea3946efdf4c@titan.jitaku.localdomain> (raw)
In-Reply-To: <644ef2b1069fabf217cddbfd75b14cae@felloff.net>
> state. the vesa bios might initialze registers that the igfx
> driver misses.
I havn't find this yet, however I found the vesa driver also set the GMBUS port as 2
same as your code.
It's like: (comments were written by me)
-----
wport 03c4 01 # VGA_SRX
rport 03c4 0001 # VGA_SRX
wport 03c4 2001 # VGA_SRX
wport ff00 00071424 # software Flag Reg 15
rport ff04 00000041 #
wport ff00 00005108 # GMBUS2 Status Reg
rport ff04 00000000 # read operation, not a wait phase, no slave timeout occured, int not occured
wport ff00 00005100 # GMBUS0 clock/Port select
rport ff04 00000000 # default (None is selected)
wport ff04 00000002 # set it to 2 (=Rate=100KHz and Dedicated to Analog Monitor DDC pins)
wport ff00 00005108 # GMBUS2 Status Reg
rport ff04 00008000 # GMBUS2 is in use by someone(default value)
wport ff00 00005104 # GMBUS1 Command/Status
------
I'm still working.
Kenji
next prev parent reply other threads:[~2016-06-22 0:25 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 [this message]
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=f27b74bf681847c960fbea3946efdf4c@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).