From owner-freebsd-current@FreeBSD.ORG Thu Oct 6 11:21:58 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 D81C916A41F for ; Thu, 6 Oct 2005 11:21:58 +0000 (GMT) (envelope-from current@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EF2943D49 for ; Thu, 6 Oct 2005 11:21:57 +0000 (GMT) (envelope-from current@dino.sk) Received: from tablet.dino.sk ([213.215.74.194]) (AUTH: PLAIN milan, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by bsd.dino.sk with esmtp; Thu, 06 Oct 2005 13:22:51 +0200 id 0000022E.4345090B.0000760F From: Milan Obuch To: freebsd-current@freebsd.org Date: Thu, 6 Oct 2005 13:21:33 +0200 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510061321.35170.current@dino.sk> Subject: 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, 06 Oct 2005 11:21:59 -0000 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/... Milan