From owner-freebsd-current@FreeBSD.ORG Thu Oct 13 20:14:54 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 8DAB716A41F for ; Thu, 13 Oct 2005 20:14:54 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E00F43D45 for ; Thu, 13 Oct 2005 20:14:54 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Thu, 13 Oct 2005 16:31:15 -0400 From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 13 Oct 2005 15:51:45 -0400 User-Agent: KMail/1.8.2 References: <200510061321.35170.current@dino.sk> In-Reply-To: <200510061321.35170.current@dino.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510131551.46397.jhb@freebsd.org> Cc: Milan Obuch Subject: Re: pcf module problem 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: Thu, 13 Oct 2005 20:14:54 -0000 On Thursday 06 October 2005 07:21 am, Milan Obuch wrote: > While working on ACCESS.bus support for Geode based WRAP boards I run into > some linker issue. As Geode's controller is full hardware implementation, I > used pcf as a template, sort of. > > After I put my base module infrastructure together and began work with > actual hardware functions and iicbus interface, my module no longer > kldloaded. > > Then I checked pcf module and found the same behavior. If you have no > 'device iicbus' in kernel configuration, issuing 'kldload pcf' gives > link_elf: symbol iicbus_intr undefined > kldload: can't load pcf: No such file or directory. > > Adding 'device iibus' into kernel configuration and rebuilding kernel fixes > this, so it looks like symbol is just not exported. > > As I am using module for development and resulting code will be built in > kernel in application platform (most probably), it is not big issue to me. > I use found work-around. It would be just nice to get this fixed. > > Anyway, is anybody out there using pcf? There is some work done in this > area, but not yet linked into main tree. I have not pcf hardware, so I can > not test anything in this area, but it would be good to make the transition > from older i386/isa/pcf.c to new dev/pcf/... Sounds like it is missing a 'MODULE_DEPEND(iicbus, 1, 1, 1);' line. Can you try adding one and seeing if it fixes the kldload of pcf? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org