From owner-cvs-src@FreeBSD.ORG Fri Feb 4 07:28:39 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AD5F16A4CE; Fri, 4 Feb 2005 07:28:39 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CFEF43D4C; Fri, 4 Feb 2005 07:28:39 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id j147SdwP030186; Thu, 3 Feb 2005 23:28:39 -0800 (PST) (envelope-from marcel@xcllnt.net) In-Reply-To: <420322CA.3090201@root.org> References: <20050204063905.8AE4716A4E9@hub.freebsd.org> <42031DC4.3000109@root.org> <420322CA.3090201@root.org> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <84e9ba659174ea3f7c7b2930c0ae3759@xcllnt.net> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Thu, 3 Feb 2005 23:28:39 -0800 To: Nate Lawson X-Mailer: Apple Mail (2.619.2) cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ia64/ia64 machdep.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Feb 2005 07:28:39 -0000 On Feb 3, 2005, at 11:22 PM, Nate Lawson wrote: >> BTW, I still have a link error: >> pluto2# make >> linking kernel.debug >> acpi_cpu.o(.text+0x2302): In function `acpi_cpu_startup': >> ../../../dev/acpica/acpi_cpu.c:757: undefined reference to >> `cpu_devclass' >> acpi_cpu.o(.data+0x1a8): In function `acpi_cpu_probe': >> ./bus_if.h:107: undefined reference to `cpu_devclass' >> *** Error code 1 >> Stop in /q/6.x/src/sys/ia64/compile/PLUTO2. >> Can it be that you missed a file? > > No, it's something I need to fix one way or the other and had on my > todo list. Ok,I'll go back to backing for my ski trip then :-) > I'm not sure if my approach is correct -- should different drivers for > the same hardware share the same devclass? A datapoint: sio(4) and uart(4) are different drivers for the same hardware. They don't share the devclass. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net