From owner-freebsd-current Sat Mar 13 2:21:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 9D03614BDA for ; Sat, 13 Mar 1999 02:21:29 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.2/8.9.2) with ESMTP id MAA13346; Sat, 13 Mar 1999 12:21:05 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.3/8.9.3) with ESMTP id MAA25837; Sat, 13 Mar 1999 12:21:06 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199903131021.MAA25837@greenpeace.grondar.za> To: Mike Smith Cc: Valentin Shopov , current@freebsd.org Subject: Re: pcic.c & {,un}register_pcic_intr declarations In-Reply-To: Your message of " Fri, 12 Mar 1999 23:45:19 PST." <199903130745.XAA00785@dingo.cdrom.com> References: <199903130745.XAA00785@dingo.cdrom.com> Date: Sat, 13 Mar 1999 12:21:05 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > 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. If that is the case, then the documentation and people's ideas differ dramatically from reality. As I said, I have a nicely working Libretto here. The configs could be tidier, and more of the kernel could be KLD, but it works almost as well as PAO did 7 months ago, and this is -CURRENT :-). > > 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). Fooey :-(. Smells like a kernel registry-of-loaded-bits is needed? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message