From owner-cvs-src@FreeBSD.ORG Fri Dec 5 11:03:13 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D51B16A4CF for ; Fri, 5 Dec 2003 11:03:13 -0800 (PST) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 148E743FEC for ; Fri, 5 Dec 2003 11:03:02 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 26627 invoked from network); 5 Dec 2003 19:03:01 -0000 Received: from unknown (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Dec 2003 19:03:01 -0000 Received: from hydrogen.funkthat.com (ilclej@localhost.funkthat.com [127.0.0.1])hB5J30gP009093; Fri, 5 Dec 2003 11:03:00 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id hB5J2xN1009092; Fri, 5 Dec 2003 11:02:59 -0800 (PST) Date: Fri, 5 Dec 2003 11:02:59 -0800 From: John-Mark Gurney To: John Baldwin Message-ID: <20031205190259.GM54398@funkthat.com> References: <20031204210904.GI54398@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: "M. Warner Losh" cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/i386 machdep.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2003 19:03:13 -0000 John Baldwin wrote this message on Fri, Dec 05, 2003 at 11:23 -0500: > The problem (which you didn't read in my mail I guess) is that the > fact that madt.ko is in its own module shouldn't be user visible. > The user should just say "load ACPI' and all the right magic should > happen. Well, now that you restate it, it's more clear. I got confused with your talking about linking issues, and other stuff, not just that issue. I was going to say, why don't you just call linker_load_module("madt.ko", NULL, NULL, NULL, NULL) from acpi and ignore the return code. Then if the module exists, it's loaded, if it doesn't, nothing changes... But this is problematic since SI_SUB_KMEM is significantly earlier than SI_SUB_KLD.. > > is thinking of) attachment... Then madt would become a device off the > > acpi bus... If acpi can detect the presence of madt (self identifing > > bus), it can create the device node for madt to attach too... if acpi > > can't, then you use an identify function in the madt code to create > > the device node off the acpi bus... > > new-bus doesn't exist yet when we probe CPUs. Again, you haven't > actually looked at how this stuff works. I realized that shortly after I sent off the email that we might be a bit earlier than the vm subsystem and friends have been setup for newbus. Ok, now I'm completely confused, why is ACPI mentioned sooo much when the apic code that madt uses doesn't reference ACPI?? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."