From owner-acpi-jp@jp.freebsd.org  Fri Sep 29 23:50:08 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id XAA41773;
	Fri, 29 Sep 2000 23:50:08 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (daemon@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id XAA41765;
	Fri, 29 Sep 2000 23:50:06 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (iwasaki.imasy.or.jp [202.227.24.92])
	by tasogare.imasy.or.jp (8.10.2+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e8TEo4r21110;
	Fri, 29 Sep 2000 23:50:04 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: tshiozak@astec.co.jp
Cc: acpi-jp@jp.freebsd.org, iwasaki@jp.freebsd.org, msmith@freebsd.org,
        haro@tk.kubota.co.jp, takawata@shidahara1.planet.sci.kobe-u.ac.jp,
        current@freebsd.org
In-Reply-To: <20000929.224139.70178011.tshiozak@astec.co.jp>
References: <200009290916.e8T9GmA04415@mass.osd.bsdi.com>
	<20000929220517P.iwasaki@jp.FreeBSD.org>
	<20000929.224139.70178011.tshiozak@astec.co.jp>
X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000929234722R.iwasaki@jp.FreeBSD.org>
Date: Fri, 29 Sep 2000 23:47:22 +0900
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 26
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 694
Subject: [acpi-jp 694] Re: ACPI megapatch
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: iwasaki@jp.freebsd.org

Hi,

> > I'd like to move and rename them as I said in my previous mail,
> > <sys/acpi.h> -> <sys/dev/acpi/acpi.h>
> > 	shared by both kernel and userland programs
> > <sys/dev/acpi/acpi.h> -> <sys/dev/acpi/acpivar.h>
> > 	shared within kernel code (acpi stuff and related drivers)
> 
> IMHO, it's desirable to use the name "acpi.h", because of conflict
> with the file dumped by /usr/sbin/config.
> 
> I love :
>   fooreg.h : device dependent and implementation independent
>              structures, macros, and others.
>   foovar.h : implementation dependent ones.

Thanks Shiozaki-san, I think `reg' is short for registers of the
target chip, correct?  In ACPI's case, PM1 register and some such
and maybe definitions for ACPI tables.
How about kernel/userland shareable stuff like ioctl?  for example,
usb(4) has this kind of definitions in dev/usb/usb.h, not in usbreg.h.
Is this a special case violating the guideline?
I think we can distinguish them like "usb.h" and <dev/usb/usb.h>,
also we will stop generating acpi.h in kernel build directory.

Thanks
