From owner-freebsd-x11@FreeBSD.ORG Sun Mar 21 10:06:26 2010 Return-Path: Delivered-To: x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F396C106564A; Sun, 21 Mar 2010 10:06:25 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id A6D148FC0C; Sun, 21 Mar 2010 10:06:25 +0000 (UTC) Received: by pwj4 with SMTP id 4so3568360pwj.13 for ; Sun, 21 Mar 2010 03:06:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Er2Jqr1AK7eCP9QDdhP4BPlLr43LxgnM5Du6H26yH5o=; b=I2Z8+cDeySKnpbA0vpknSxuOKc6lTuuC0p5hXEfiyOgYqsxTJVdGn87+jFbLDOfgNp cXa9kgEv3vj+XV9pm1KhUfCinmuRhMLxA0vkJrMJaaPYQ3v2JOZ79nRKnl9FFRh+VxU7 eE8beP19/Z4PIxIaKULHjc0WdqvgEmshjx1Vs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mTCqNc/InwKLWWih27COrBWg/QYGISUeeTkZFa3/GcNJJvJgIsoK1HBKIz49PADJE7 FY3sRllo0Ncsmi33Q8tA28zjgjAd6u5x/pLRAk5FKX+pMBn/P9IoeHVOvZ4YDwDxkRPz eAbigjD0jnrdwIvJnuC4a7Azytt1doZHmqIOg= MIME-Version: 1.0 Received: by 10.143.153.42 with SMTP id f42mr830938wfo.299.1269165985189; Sun, 21 Mar 2010 03:06:25 -0700 (PDT) In-Reply-To: References: <20100311134413.GH19740@bsdcrew.de> <1268414671.2608.293.camel@balrog.2hip.net> <1268484504.2608.309.camel@balrog.2hip.net> <1268625423.2608.348.camel@balrog.2hip.net> Date: Sun, 21 Mar 2010 03:06:25 -0700 Message-ID: <7d6fde3d1003210306p163f4751h2ab306cb3b72e202@mail.gmail.com> From: Garrett Cooper To: jhell Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Torfinn Ingolfsen , ports@freebsd.org, x11@freebsd.org Subject: Re: [Call for Testing] X.org 7.5 for FreeBSD X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2010 10:06:26 -0000 On Sun, Mar 21, 2010 at 2:42 AM, jhell wrote: > > On Sun, 14 Mar 2010 23:57, Robert Noland wrote: > In Message-Id: <1268625423.2608.348.camel@balrog.2hip.net> > >> On Sun, 2010-03-14 at 15:02 -0600, Warren Block wrote: >>> >>> On Sat, 13 Mar 2010, Robert Noland wrote: >>> >>>> Ok, now that agp seems to be working... I have created a port for the >>>> 2.9.1 version of the Intel driver. =A0You will need to uninstall the >>>> existing intel driver and install this one. =A0You still won't have dr= m, >>>> but should be a good bit better than vesa... >>>> >>>> http://people.freebsd.org/~rnoland/xf86-video-intel29.tar.gz >>> >>> Problem: after switching away from X with ctrl-alt-f4, on switching bac= k >>> the screen is corrupted. =A0Stuff that's drawn on top of it after that >>> point is usually correct. =A0The clear areas on this image were caused = by >>> GIMP redrawing them; before opening it, they were the same as the strip >>> on the right edge. >> >> Ok, I'm not surprised... I spent a little time playing with the 2.9.1 >> driver on my g45 today. =A0Basically... It is horrid... >> > > Damn! I rely on this driver for my main machine that has a i845G in it. T= his > thing tends to keep getting more shitty with every release. Or I suppose = I > could cough it up to ancient hardware to... ;) > > The last Intel driver I remember working seamlessly with my i845G with no > known side effects and without HAL was 2.3*. After that it somehow became > very dependent on HAL and if compiled without HAL would pretty much disab= le > you(being me) from switching from X to the console and back again resulti= ng > in a reboot after a borked screen. > > Now that I see the following I sort of understand whats happening with th= is. > And eventually this hardware will have to be replaced :( > >> When Intel chose to remove all non-GEM support for the 2.8 series >> driver, what is actually going on is that it is calling into >> libdrm_intel's fake buffer manager and doing ton's of memcpy's. =A0It >> seems to be sort of ok as long as it is just basic 2d, but enable >> composite in metacity and it falls on it's face... =A0Granted all of my >> machines run with WITNESS and INVARIANTS, but you can almost count the >> pixels as they are drawn... >> >> I was thinking that Intel had actually killed the fake buffer manager as >> well, but it looks like it does still exist in libdrm git. =A0Perhaps it >> was that they removed it from mesa. =A0At any rate, they don't deny that >> it is broken, nor do they test it or have any intention of fixing it... >> >> The only reason for using the 2.9.1 driver that I can think of is if you >> have an Ironlake chipset, which isn't supported in 2.7.1. =A0I now have = to >> decide whether to spend time back porting Ironlake support to 2.7.1 or >> spend time on GEM. Intel's killing off non-GEM support slowly and surely, so we have to port GEM or die a slow and painful death on Intel accelerated hardware: http://www.phoronix.com/scan.php?page=3Dnews_item&px=3DNjc2NA , http://software.intel.com/sites/oss/project_spotlight.htm . Kind of sad now that anholt is no longer really a contributing member to FreeBSD. Thanks, -Garrett