From owner-freebsd-current@freebsd.org Thu Sep 17 21:42:05 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DEDF9CEE3E for ; Thu, 17 Sep 2015 21:42:05 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD13117C1 for ; Thu, 17 Sep 2015 21:42:04 +0000 (UTC) (envelope-from n.pajkovsky@gmail.com) Received: by wicfx3 with SMTP id fx3so7982159wic.0 for ; Thu, 17 Sep 2015 14:42:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=NW+YEPRwQqTH0D0FVrYjrLEin1S0T/wt5yjDtXYCHIY=; b=zlwkaA8fAW2Y1IGI5ulz1s/qieKkpBWZgr/+QwDH5V5sgcXD5FEiHg5cyGaoapQRwZ Sl9xKvWlV1kE8pppnZo8im90bUZT/x5ZykZegCgcbuK5HNIlPcEjEsy7kKc5uQ8Mbqyl WgI18ZYi7T46lhRoTXhl1PAjC9vOqx91qO/gQ3p5uKm6rs/hEJHmZjGT3lSlCRrUtbsi 0lrcKEskfpLYVzAMu9lALoZBAGuwFNkUmuVC6eLUFY+/aj+kF3gSKAMLivtrfbwQrZPL UfGhNn7RXvgPjCDl5LafwYz1ovVg3g1uHWkJyehtIvIj8qMar4eK+QjPJdymyBa5DyXS 23eA== X-Received: by 10.180.81.199 with SMTP id c7mr11578261wiy.87.1442526123104; Thu, 17 Sep 2015 14:42:03 -0700 (PDT) Received: from localhost (ip-94-112-33-45.net.upcbroadband.cz. [94.112.33.45]) by smtp.gmail.com with ESMTPSA id fr10sm12117965wib.14.2015.09.17.14.42.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Sep 2015 14:42:01 -0700 (PDT) From: Nikola Pajkovsky To: Stefan Wendler Cc: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? References: <55FA7324.5010603@icloud.com> <55FADB38.7000406@pcbsd.org> <87twqt2gs9.fsf@gooddata.com> <11271727.FrCOrXGY1l@hactar> Date: Thu, 17 Sep 2015 23:42:01 +0200 In-Reply-To: <11271727.FrCOrXGY1l@hactar> (Stefan Wendler's message of "Thu, 17 Sep 2015 19:28:14 +0200") Message-ID: <87a8sk205y.fsf@gooddata.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Sep 2015 21:42:05 -0000 Stefan Wendler writes: > On Thursday 17 September 2015 17:43:02 Nikola Pajkovsky wrote: > >> Use memcontrol to set mtrr write-combine for your Vesa. Vesa is lightning >> fast on T440p on 1920x1200. > > I use a T540 and didn't get this to work yet. Can you give me the commands > you've used? I guess we have the same chips anyway. So the hex-values should > be the same? Do not run those commands in X, otherwise it hangs. $ vidcontrol -i mode | grep 1920 383 (0x17f) 0x0000000f G 1920x1080x32 D 8x16 0xa0000 64k 64k 0xe0000000 8100k $ memcontrol list | grep 0xe0000000 0xe0000000/0x20000000 BIOS uncacheable set-by-firmware active $ memcontrol set -b 0xe0000000 -l 0x20000000 -o BIOS write-combine $ startx -- Nikola