From owner-acpi-jp@jp.freebsd.org  Thu Mar 22 10:05:11 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id KAA24768;
	Thu, 22 Mar 2001 10:05:11 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.dis.org ([206.112.127.152])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id KAA24762
	for <acpi-jp@jp.freebsd.org>; Thu, 22 Mar 2001 10:05:09 +0900 (JST)
	(envelope-from msmith@mass.dis.org)
Received: from mass.dis.org (localhost [127.0.0.1])
	by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2M13tE00704
	for <acpi-jp@jp.freebsd.org>; Wed, 21 Mar 2001 17:03:58 -0800 (PST)
	(envelope-from msmith@mass.dis.org)
Message-Id: <200103220103.f2M13tE00704@mass.dis.org>
X-Mailer: exmh version 2.1.1 10/15/1999
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Wed, 21 Mar 2001 16:54:17 PST."
             <4148FEAAD879D311AC5700A0C969E8905DE79A@orsmsx35.jf.intel.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 21 Mar 2001 17:03:55 -0800
From: Mike Smith <msmith@freebsd.org>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 1115
Subject: [acpi-jp 1115] Re: acpica-unix-20010313.tar.gz 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> > absorb this thread, will be bringing it in.  Intel did us 
> > something of a 
> > big disfavour by moving everything around, as it's going to 
> > make a mess 
> > in the repo, but fortunately we haven't tagged anything yet. 8)
> 
> Um, yeah, sorry.

That's OK.  I assume you had a good reason for it.  You need to fix the 
include paths though, since you have inconsistent assumptions about 
include/platform (in some places you assume it's in the include path, in
others you explicitly refer to platform/foo.h).

> One thing you might consider (maybe short-term, perhaps long-term) is
> figuring out how you want the code, and then scripting up something that
> makes a given release into that. I have a couple of good-size scripts that
> do this for me, regarding the Linux patches.

I'm actually kinda loth to do this, as it means that what we'd have on 
our vendor branch is the post-processed version of the code, rather than 
your actual public releases.  Unless you're planning on changing 
everything again, of course. 8)

(topic switch)
We actually need to do something about the way we build the ACPI code, 
though, as we currently spam the include path into the entire kernel 
build.  I've been talking with Peter Wemm about this, and I think we 
might build it as a module (to a .kld) and then link it with the kernel.

Another thought was to only build it as a module and have the loader 
bring it in as required.  

Regards,
Mike
-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E


