From owner-freebsd-current@FreeBSD.ORG Fri Sep 18 01:57:32 2009 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 082BB106568D; Fri, 18 Sep 2009 01:57:32 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (mail.farley.org [IPv6:2001:470:1f0f:20:2::11]) by mx1.freebsd.org (Postfix) with ESMTP id A4A898FC08; Fri, 18 Sep 2009 01:57:31 +0000 (UTC) Received: from thor.farley.org (HPooka@thor.farley.org [IPv6:2001:470:1f0f:20:1::5]) by mail.farley.org (8.14.3/8.14.3) with ESMTP id n8I1vUlq038288; Thu, 17 Sep 2009 20:57:30 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Thu, 17 Sep 2009 20:57:30 -0500 (CDT) From: "Sean C. Farley" To: Robert Noland In-Reply-To: <1253237945.2038.421.camel@balrog.2hip.net> Message-ID: References: <20090917134924.GZ1212@albert.catwhisker.org> <20090917170431.47be4a06@ernst.jennejohn.org> <20090917152957.GA1212@albert.catwhisker.org> <20090917161519.GB1212@albert.catwhisker.org> <20090917235322.GM1212@albert.catwhisker.org> <1253237945.2038.421.camel@balrog.2hip.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-2.8 required=4.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail.farley.org Cc: current@FreeBSD.org Subject: Re: misc/compat6x port no longer sufficient for DRI under head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 18 Sep 2009 01:57:32 -0000 On Thu, 17 Sep 2009, Robert Noland wrote: > On Thu, 2009-09-17 at 20:13 -0500, Sean C. Farley wrote: *snip* >> WITHOUT_HAL throughout ports, dbus running and the option I listed >> above works well for me with stable/7 (r196739). > > Just to be clear... hald has a number of build time features and > tweaks depending on current OS support, so I'm not really surprised > that hald doesn't work well or correctly in David's case. > > hald has no interaction with drm though, other than if hald is running > it will try to open drm and get the driver version. hald certainly > wouldn't have any impact of X functioning or not based on the DRI > option. > > The evidence so far seems to be pointing to some issue with setting > MTRR, though I'm not exactly certain how or what is failing. I understand. I did not necessarily consider hald to be culprit in relation to the DRI option. However, building ports without HAL may (or may not) be useful in the situation where hald from 6.0 is being run on 7.0 and 8.0, especially since hald has build-time specifics based upon the OS version. Sean -- scf@FreeBSD.org