From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 16 22:57:17 2005 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9831716A420; Fri, 16 Dec 2005 22:57:17 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78D0F43D45; Fri, 16 Dec 2005 22:57:16 +0000 (GMT) (envelope-from ohartman@mail.uni-mainz.de) Received: from [83.242.62.175] (175-62-242-83.dip.h-tel.de [83.242.62.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 9FCEF30018F5; Fri, 16 Dec 2005 23:57:13 +0100 (CET) Message-ID: <43A34647.1030404@mail.uni-mainz.de> Date: Fri, 16 Dec 2005 23:57:11 +0100 From: "O. Hartmann" User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <43A1636A.6030108@mail.uni-mainz.de> <200512161230.41499.jkim@FreeBSD.org> <43A30B25.3030102@mail.uni-mainz.de> <200512161422.00688.jkim@FreeBSD.org> In-Reply-To: <200512161422.00688.jkim@FreeBSD.org> Content-Type: multipart/mixed; boundary="------------000605030806080300050400" X-Virus-Scanned: by amavisd-new at uni-mainz.de X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-amd64@FreeBSD.org Subject: Re: device drm with PCIe? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 22:57:17 -0000 This is a multi-part message in MIME format. --------------000605030806080300050400 Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit Jung-uk Kim wrote: >On Friday 16 December 2005 01:44 pm, O. Hartmann wrote: > > >>Jung-uk Kim schrieb: >> >> >>>On Thursday 15 December 2005 07:36 am, O. Hartmann wrote: >>> >>> >>>>Normally 'device drm' is only useable in conjunction with 'device >>>>agp'. A lot of amd64 based boxes now use PEG slots for their >>>>graphics accelerators. Is it possible to utilize 'drm' with PCIe >>>>devices? >>>> >>>> >>>Yes. It should work, at least in theory. ;-) >>> >>> >>> >>>>Does device agp has any effect on PCIe graphics accelerators? >>>> >>>> >>>No. You don't need it for PCI-Express controller. >>> >>> >>Ok, but without AGP (device agp) in my kernel config file, I get a >>lot of errors while linking the kernel of missing agp_xxxxx >>routines (FreeBSD 6.0-STABLE/amd64). So, device drm alone seems to >>be useless (although in conjunction with device pci). >> >> > >Did you try 'make clean; make cleandepend; make depend; make'? > > Doesn't work without device agp in kernel config file! linking kernel drm_agpsupport.o(.text+0x22c): In function `drm_agp_info': : undefined reference to `agp_get_info' drm_agpsupport.o(.text+0x324): In function `drm_agp_acquire': : undefined reference to `agp_acquire' drm_agpsupport.o(.text+0x374): In function `drm_agp_release': : undefined reference to `agp_release' drm_agpsupport.o(.text+0x3cf): In function `drm_agp_enable': : undefined reference to `agp_enable' drm_agpsupport.o(.text+0x45b): In function `drm_agp_init': : undefined reference to `agp_find_device' drm_agpsupport.o(.text+0x4ed): In function `drm_agp_init': : undefined reference to `agp_get_info' drm_agpsupport.o(.text+0x534): In function `drm_agp_allocate_memory': . . . . drm_agpsupport.o(.text+0xb66): In function `drm_agp_unbind_memory': : undefined reference to `agp_unbind_memory' *** Error code 1 Stop in /usr/obj/usr/src/sys/THOR. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. >Jung-uk Kim > > > >>>Jung-uk Kim >>> >>> >>> >>>>Thanks, >>>>Oliver >>>> >>>> --------------000605030806080300050400--