From owner-freebsd-current Fri Mar 12 23:28:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles218.castles.com [208.214.165.218]) by hub.freebsd.org (Postfix) with ESMTP id 232E314D60 for ; Fri, 12 Mar 1999 23:28:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA00672; Fri, 12 Mar 1999 23:21:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903130721.XAA00672@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray Cc: Mike Smith , Valentin Shopov , current@freebsd.org Subject: Re: pcic.c & {,un}register_pcic_intr declarations In-reply-to: Your message of "Sat, 13 Mar 1999 09:19:56 +0200." <199903130719.JAA20951@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Mar 1999 23:21:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > The only configuration which currently works correctly is to remove the > > kldload of the pcic module from /etc/rc.pccard and compile everything > > else statically into the kernel. > > > > Every other variation is *broken*. > > Nope. I am kldloading pcic on my Libretto with no problems at all. > I have no private hacks on that machine _at_all_. The only brokenness > is when users compile pcic into the kernel, and rc.pccard kldloads > pcic (Which is my stuffup). Unfortunately, no, that's not correct. The pcic module contains a reference to a symbol that's only present in the kernel when the card* devices are statically compiled in. Ie. if you remove pcic* and card* you can't load the pcic module. This makes the pcic module useless, and, as I said, renders any combination other than 100% static *broken*. > Two solutions; 1) don't compile pcic into your kernel; 2) remove the > kldload pcic from rc.pccard; 3) fix kldload to not load modules when > their functionality is already compiled in (_Three_ Solutions!!). 1) is a non-solutuion. 3) is where the correct answer lies, but until the file/module dichotomy is resolved, it's not possible to do that. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message