From owner-acpi-jp@jp.FreeBSD.org Fri Dec 19 05:53:28 2003
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id hBIKrS134682;
	Fri, 19 Dec 2003 05:53:28 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from rootlabs.com (root.org [67.118.192.226])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with SMTP/inet id hBIKrRC34676
	for <acpi-jp@jp.freebsd.org>; Fri, 19 Dec 2003 05:53:27 +0900 (JST)
	(envelope-from nate@rootlabs.com)
Received: (qmail 74408 invoked by uid 1000); 18 Dec 2003 20:53:22 -0000
From: Nate Lawson <nate@root.org>
To: arch@freebsd.org
cc: acpi-jp@jp.FreeBSD.org
Message-ID: <20031218124754.O74387@root.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Thu, 18 Dec 2003 12:53:22 -0800
X-Sequence: acpi-jp 2926
Subject: [acpi-jp 2926] acpi_toshiba and acpi_asus drivers
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: nate@root.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+031216

I'm prepping/reworking some user-submitted drivers for import.  I'd like
some comments on the directory structure.  The hardware both drive is
everything from fans to hotkeys to lcd backlight.  Both are very
hw-specific and do not conform to the ACPI spec although they do control
their functions through ACPI.

The directory structure I'm currently working with is:
    sys/i386/acpica/acpi_toshiba.c
    sys/i386/acpica/acpi_asus.c
    sys/modules/acpi_toshiba/Makefile
    sys/modules/acpi_asus/Makefile
    share/man/man4/acpi_toshiba.4
    share/man/man4/acpi_asus.4

One alternative is to their modules under the acpi dir (e.g.,
sys/modules/acpi/acpi_toshiba).  Also, the driver src could be
sys/dev/acpi_toshiba.  However, a new dir for just one file seems a bit
much.  My main concern is that as these drivers proliferate that we keep
the dir structure neat.

Thanks,
Nate
