From owner-freebsd-i386@FreeBSD.ORG  Tue Sep 14 10:43:56 2004
Return-Path: <owner-freebsd-i386@FreeBSD.ORG>
Delivered-To: freebsd-i386@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7C94D16A4D2
	for <freebsd-i386@freebsd.org>; Tue, 14 Sep 2004 10:43:56 +0000 (GMT)
Received: from neuronfire.org (neuronfire.org [213.78.141.73])
	by mx1.FreeBSD.org (Postfix) with SMTP id 3B52E43D2D
	for <freebsd-i386@freebsd.org>; Tue, 14 Sep 2004 10:43:55 +0000 (GMT)
	(envelope-from dsw@neuronfire.org)
Received: (qmail 3370 invoked by uid 1000); 14 Sep 2004 10:43:45 -0000
Date: Tue, 14 Sep 2004 11:43:45 +0100
From: dsw <dsw@neuronfire.org>
To: freebsd-i386@freebsd.org
Message-ID: <20040914104345.GA14229@neuronfire.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2i
Subject: 
	make buildkernel 5.2.1 -> 5.3-BETA3 error (mem_range_attr_set / DRM)
X-BeenThere: freebsd-i386@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: I386-specific issues for FreeBSD <freebsd-i386.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-i386>
List-Post: <mailto:freebsd-i386@freebsd.org>
List-Help: <mailto:freebsd-i386-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2004 10:43:56 -0000

Hi List,

Going from 5.2.1-RELEASE to 5.3-BETA3, and compiling a non-SMP custom kernel with
radeondrm I get the following breakage:

...snip...

linking kernel
radeon_drv.o(.text+0x5346): In function `radeon_mtrr_add':
: undefined reference to `mem_range_attr_set'
radeon_drv.o(.text+0x53a2): In function `radeon_mtrr_del':
: undefined reference to `mem_range_attr_set'

I saw a recent thread where Robert Watson committed a change to mp_machdep.c
and machdep.c which fixed a /similar/ error, but this seems unrelated.

I have checked out the RELENG_5 tree from scratch just in case there was
any cruft left from 5.2.1, but still the same error.. 

Has anyone else seen/fixed this?

Cheers

D.

-- 
Brennen der bruecken.