From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta01.eonet.ne.jp ([203.140.81.44]) by ur; Thu Jul 28 19:49:06 EDT 2016 Received: from ci5dell.jitaku.localdomain (101-141-38-118f1.osk3.eonet.ne.jp [101.141.38.118]) by mailmsa11.mozu.eo.k-opti.ad.jp with ESMTP id u6SNmxJh008768 for <9front@9front.org>; Fri, 29 Jul 2016 08:49:00 +0900 To: 9front@9front.org Subject: Re: [9front] core-i5(TypeSNB) and vesa mode Date: Fri, 29 Jul 2016 08:48:59 +0900 From: kokamoto@hera.eonet.ne.jp Message-ID: <75fa8290562b7eadf03d9d403da4ac58@ci5dell.jitaku.localdomain> In-Reply-To: <18968ec970b59f46e65e46781b65e5c0@felloff.net> References: <18968ec970b59f46e65e46781b65e5c0@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: YAML general-purpose GPU backend > its just two functions. gen6_fdi_link_train() is called frist, which > exercises training pattern 1 and 2. after that, intel_fdi_normal_train() > is called which switches to link train pattern normal mode. It sounds like the same as I did here. I'm not interested now on it, because I have now another problem of stability of high resolution(up to 1680x1050x32). Kenji