From owner-acpi-jp@jp.FreeBSD.org Fri Oct 25 03:48:32 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g9OImWv09706;
	Fri, 25 Oct 2002 03:48:32 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g9OImT309698
	for <acpi-jp@jp.FreeBSD.org>; Fri, 25 Oct 2002 03:48:29 +0900 (JST)
	(envelope-from jhb@FreeBSD.org)
Received: (qmail 2623 invoked from network); 24 Oct 2002 18:48:34 -0000
Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63])
          (envelope-sender <jhb@FreeBSD.org>)
          by mail14.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP
          for <acpi-jp@jp.FreeBSD.org>; 24 Oct 2002 18:48:34 -0000
Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1])
	by server.baldwin.cx (8.12.6/8.12.6) with ESMTP id g9OImOn5071870;
	Thu, 24 Oct 2002 14:48:25 -0400 (EDT)
	(envelope-from jhb@FreeBSD.org)
Message-ID: <XFMail.20021024144823.jhb@FreeBSD.org>
X-Mailer: XFMail 1.5.2 on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <E0FF1663-E77F-11D6-B5AD-0050E4660701@freebsd.org>
From: John Baldwin <jhb@freebsd.org>
To: Michael Smith <msmith@freebsd.org>
Cc: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>, acpi-jp@jp.FreeBSD.org
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Thu, 24 Oct 2002 14:48:23 -0400
X-Sequence: acpi-jp 1906
Subject: [acpi-jp 1906] RE: Any objections to renaming 'device acpica
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: jhb@FreeBSD.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+021018


On 24-Oct-2002 Michael Smith wrote:
> 
> On Thursday, October 24, 2002, at 11:12 AM, John Baldwin wrote:
> 
>> On 24-Oct-2002 Mitsuru IWASAKI wrote:
>>>> Are there any objections to renaming the new-bus ACPI device
>>>> from acpica to acpi to match the character device, kernel module,
>>>> and manpage names?
>>>
>>> I have no objections.
>>> And how about changing sys/dev/acpica/ to sys/dev/acpi/ ?
>>
>> Hmm good point.  I can do that as well if desired.  I think the
>> contrib code should stay where it is since Intel's code drop
>> is called ACPICA.
> 
> IMO, it should always be a module and never actually compiled into
> the kernel.  But calling it 'acpi' would be fine.

I find that with all the various kernels I compile it is far too
easy for me to blow my foot off if I use modules.  Also easier
for debugging if I use static kernels.  Also things like INVARIANTS,
etc. don't get turned on in modules w/o hacking.  This is currently
more a fault of our kernel build framework though and static kernels
are simply a workaround for that. :)

-- 

John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/
