Date: Fri, 29 Sep 2000 23:47:22 +0900 From: Mitsuru IWASAKI <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 Subject: Re: ACPI megapatch Message-ID: <20000929234722R.iwasaki@jp.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000929234722R.iwasaki>