From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta01.eonet.ne.jp ([203.140.81.47]) by ur; Thu Jul 28 07:32:02 EDT 2016 Received: from titan.jitaku.localdomain (101-141-38-118f1.osk3.eonet.ne.jp [101.141.38.118]) by mailmsa12.mozu.eo.k-opti.ad.jp with ESMTP id u6SBVsN6025741 for <9front@9front.org>; Thu, 28 Jul 2016 20:31:55 +0900 To: 9front@9front.org Subject: Re: [9front] core-i5(TypeSNB) and vesa mode Date: Thu, 28 Jul 2016 20:31:53 +0900 From: kokamoto@hera.eonet.ne.jp Message-ID: In-Reply-To: References: 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: object-oriented stateless deep-learning lifecycle CSS self-signing manager > - Enable CPU FDI Transmitter and PCH FDI Receiver with Training Pattern 1 enabled. > - Wait for FDI training pattern 1 time > - Read PCH FDI Receiver ISR for bit lock in bit 8 (retry at least once if no lock) > - Enable training pattern 2 on CPU FDI Transmitter and PCH FDI Receiver > - Wait for FDI training pattern 2 time > - Read PCH FDI Receiver ISR for symbol lock in bit 9 (retry at least once if no lock) > - Enable normal pixel output on CPU FDI Transmitter and PCH FDI Receiver > - Wait for FDI idle pattern time for link to become active I had intended to follow those lines, because I had no other guides for this. Maybe I made something wrong? Kenji PS. I'm now facing a problem to have a stable 1680x1050x32. At present I have no clue on this...