From owner-freebsd-current@freebsd.org Thu Sep 17 15:32:36 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 DD67C9CECA5 for ; Thu, 17 Sep 2015 15:32:35 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9047B1CBA for ; Thu, 17 Sep 2015 15:32:35 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1ZcbAn-003Pai-Fz>; Thu, 17 Sep 2015 17:32:33 +0200 Received: from x5ce12e0c.dyn.telefonica.de ([92.225.46.12] helo=thor.walstatt.dynvpn.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1ZcbAn-000sKq-7s>; Thu, 17 Sep 2015 17:32:33 +0200 Date: Thu, 17 Sep 2015 17:32:32 +0200 From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: Re: Intel Haswell support - Any updates? Message-ID: <20150917173232.1c9f42d9.ohartman@zedat.fu-berlin.de> In-Reply-To: <55FADB38.7000406@pcbsd.org> References: <55FA7324.5010603@icloud.com> <09A515F2-44BA-4DF0-9792-D4C56EEB9D7C@FreeBSD.org> <114F22EF-61E3-4D75-84FB-9D6E3FBCB8F3@FreeBSD.org> <20150917131333.GN1247@egr.msu.edu> <20150917134809.GA3025@c720-r276659> <55FAD5EF.5030001@pcbsd.org> <20150917171958.046e4b6b.ohartman@zedat.fu-berlin.de> <55FADB38.7000406@pcbsd.org> Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/MTrW6xd9kyiOOulhQIT9rrj"; protocol="application/pgp-signature" X-Originating-IP: 92.225.46.12 X-ZEDAT-Hint: A 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 15:32:36 -0000 --Sig_/MTrW6xd9kyiOOulhQIT9rrj Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Thu, 17 Sep 2015 11:24:40 -0400 Kris Moore schrieb: > On 09/17/2015 11:19, O. Hartmann wrote: > > Am Thu, 17 Sep 2015 11:02:07 -0400 > > Kris Moore schrieb: > > > >> On 09/17/2015 09:48, Matthias Apitz wrote: > >>> El d=C3=ADa Thursday, September 17, 2015 a las 10:41:43PM +0900, Lund= berg, Johannes > >>> escribi=C3=B3: > >>> > >>>> Same here. I would personally definitely buy new hardware from Intel= if > >>>> FreeBSD worked on it (not vesa...) > >>>> ... > >>> What dow you have against vesa? I run CURRENT on some Acer C720 > >>> Chromebooks with Haswell chipset in Vesa mode. And you will not note = it. > >>> I have never ever had such a fast desktop (KDE4) before. I can live f= ine > >>> with Vesa until Haswell suport is there. > >>> > >>> matthias > >> BTW, have you tried the xf86-video-scfb driver? It works much better > >> than vesa here. The only catch is you have to be booted UEFI with CSM > >> disabled. Using it on my X1 Carbon, gets 3k resolution properly and > >> everything. Thanks to Glen Barber for bringing that to my attention. > >> > > Running that specific driver on several Lenovo HD4600 driven models giv= es me headaches > > and more. This software-framebuffer works - yes, on whatever resolution= you might > > wish, but it consumes CPU time. That said, I recall that the display wa= s jumpy, slow > > and unresponsive when used under heavy load - not even 3k resolution, b= ut with a > > moderate lowend of 1980x1080. >=20 > Interesting, that's been the opposite of my experience here. Vesa was > much slower / using more CPU time and didn't give me the native > resolution. Switching to scfb made the laptop "usable" for me, at least > until we get a proper Intel driver that does Broadwell. >=20 ... as I said - VESA is unwilling to cooperate at higher resolutions, so I = do not have any comparison parameters fro the specific single hardware. VESA was slow i= n the past - compared to the nVidia BLOB or the X11 AMD HD 48XX drivers. --Sig_/MTrW6xd9kyiOOulhQIT9rrj Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV+t0QAAoJEOgBcD7A/5N8ro4IAJZZxWcUNPEwxTjL8KVR93k5 kqtm5cW8t1w61cXoKi+JOOfgsUS/vUO7fPnJFyjgwYwAdLDJHXQaDy+QIS58E9Dd kP6kU+s0SvC71DuyujU8C+m/pkdSUT0S9Cn7NImXMifaiWJPhX7wHfQ/BZwfL1Ym FjbRM5/MCaSyc/2uZyM3huREeH5Co1VRTYxTfekT4l074g1EwQo4aiSYri5u5sc/ 1+VFSWFLYvvvJPQwjPyUfWvuoql47mN88J+lNSFNggVPO9O1wviSWC04mhLqecwP gwK8N9Vsp5UHaBCeyApFNCP8fDbXYgcbwpkTUOX/PS7qjOfSQP6U5Ij58UhrunY= =v99z -----END PGP SIGNATURE----- --Sig_/MTrW6xd9kyiOOulhQIT9rrj--