From owner-freebsd-current Wed Jul 17 20:27:29 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BABA37B400 for ; Wed, 17 Jul 2002 20:27:27 -0700 (PDT) Received: from sccrmhc02.attbi.com (sccrmhc02.attbi.com [204.127.202.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 857B043E64 for ; Wed, 17 Jul 2002 20:27:26 -0700 (PDT) (envelope-from eta@lclark.edu) Received: from anholt ([12.224.154.76]) by sccrmhc02.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020718032725.KRQG6023.sccrmhc02.attbi.com@anholt>; Thu, 18 Jul 2002 03:27:25 +0000 Subject: Re: Problem with agpgart on current, XFree86-4, Matrox G400 video From: Eric Anholt To: Peter Wemm Cc: Garance A Drosihn , current@FreeBSD.ORG In-Reply-To: <20020718025933.4141C3811@overcee.wemm.org> References: <20020718025933.4141C3811@overcee.wemm.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 17 Jul 2002 21:27:28 -0600 Message-Id: <1026962848.40832.341.camel@anholt.dyndns.org> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 2002-07-17 at 20:59, Peter Wemm wrote: > Eric Anholt wrote: > > > This looks like the classic error of the agp module having been loaded > > by the drm because it's required, but agp doesn't probe/attach because > > a generic bridge driver has already claimed the agp device. > > I doubt that would be a problem as long as it came with a patch to the > release scripts so that the agp device was filtered out of the BOOTMFS > kernel image. (A quick grep -r for BOOTMFS should show up the sed scripts > that turn GENERIC into BOOTMFS in src/release). > > The 'agp' device isn't likely to hurt anything, is it? There's one thing in i810 I might want to check again before making it default, but other than that I think agp is pretty stable these days. I haven't heard of problems with specific AGP chipsets since the AMD fixes (MTRR + agp_amd.c) we had. The one interesting interaction I've heard of recently is that when a person had device agp in the kernel and agp_enable="YES" in loader.conf the agp device malfunctioned (probed fine according to dmesg, but the DRM couldn't find it with agp_find_device()). I could see this biting people if we didn't have an entry in UPDATING, because a lot of people have gone the loader.conf way. -- Eric Anholt http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message