From owner-freebsd-current Fri Mar 12 23:51:40 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 3EBD114E8D for ; Fri, 12 Mar 1999 23:51:37 -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 XAA00785; Fri, 12 Mar 1999 23:45:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903130745.XAA00785@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:38:43 +0200." <199903130738.JAA21046@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Mar 1999 23:45:19 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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. > > I have card* compiled in (perhaps I should have mentioned that?), and > pcic* kldloaded. > > > This makes the pcic module useless, and, as I said, renders any > > combination other than 100% static *broken*. > > Rubbish! Why is my system working? Because you have an horrific mishmash of bits; it's not meant to be broken up as you have. > > > 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. > > 1) works (and needs tidying up). > > Any suggestions for a kernel neophyte on how to get stuck into 3)? Not really; you'd need to study how KLD currently works, then go back over the discussions that Peter, Doug, I and others have had about how we might identify modules within a file, and implement it. I fear that it will result in binary incompatability (again). -- \\ 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