From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta01.eonet.ne.jp ([203.140.81.45]) by ur; Tue Jun 21 20:25:27 EDT 2016 Received: from titan.jitaku.localdomain (182-164-101-240f1.osk3.eonet.ne.jp [182.164.101.240]) by mailmsa12.mozu.eo.k-opti.ad.jp with ESMTP id u5M0PLWN013426 for <9front@9front.org>; Wed, 22 Jun 2016 09:25:21 +0900 To: 9front@9front.org Subject: Re: [9front] strange behaviour of igfx and vesa Date: Wed, 22 Jun 2016 09:25:21 +0900 From: kokamoto@hera.eonet.ne.jp Message-ID: In-Reply-To: <644ef2b1069fabf217cddbfd75b14cae@felloff.net> References: <644ef2b1069fabf217cddbfd75b14cae@felloff.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: managed structured information pipelining framework > 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