From owner-acpi-jp@jp.freebsd.org  Sat Sep 30 05:06:14 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id FAA58472;
	Sat, 30 Sep 2000 05:06:14 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from mass.osd.bsdi.com (adsl-63-202-176-106.dsl.snfc21.pacbell.net [63.202.176.106])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id FAA58466;
	Sat, 30 Sep 2000 05:06:12 +0900 (JST)
	(envelope-from msmith@mass.osd.bsdi.com)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
	by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8TK7aA06203;
	Fri, 29 Sep 2000 13:07:36 -0700 (PDT)
	(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200009292007.e8TK7aA06203@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
cc: tshiozak@astec.co.jp, acpi-jp@jp.FreeBSD.org, haro@tk.kubota.co.jp,
        takawata@shidahara1.planet.sci.kobe-u.ac.jp, current@freebsd.org
In-reply-to: Your message of "Fri, 29 Sep 2000 23:47:22 +0900."
             <20000929234722R.iwasaki@jp.FreeBSD.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 29 Sep 2000 13:07:36 -0700
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 699
Subject: [acpi-jp 699] Re: ACPI megapatch 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: msmith@freebsd.org

> > > 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.

Typically you would have:

acpivar.h	Data structures defined by implementation
acpireg.h	Data structures defined by interface
acpiio.h	Interface to userland

Since we're all in agreement, I'll move to these.

-- 
... 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


