DragonFly BSD
DragonFly submit List (threaded) for 2004-05
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: acpica5 and acpi sub-modules (Re: cvs commit: src/sys/dev Makefile)


From: YONETANI Tomokazu <qhwt+dragonfly-submit@xxxxxxxxxx>
Date: Thu, 27 May 2004 08:24:25 +0900

On Wed, May 26, 2004 at 10:01:33PM +0900, YONETANI Tomokazu wrote:
> >     The second issue is the addition of dev/acpi.  This seems to have taken
> >     over the build that used to be in acpica5.  The build should really be
> >     in acpica5 with appropriate rearrangements to accomodate your new 
> >     subdirectory structure (which I think is fine).  Putting the build
> >     in dev/acpi creates a lot of confusion between dev/acpi and dev/acpica5.
> 
> The only reason that I created dev/acpi was so as I could
> immitate /sys/modules/acpi tree in FreeBSD-CURRENT. Originally
> I was planning to populate acpi submodule directories under
> /sys/dev/acpica5 and use bsd.subdir.mk, but then, because of my
> lack of knowledge, nothing in acpica5 was compiled. IMHO calling it
> acpi is more intuitive than as acpica, but I'll try to rewrite the
> patch as you suggested. I also considered moving freebsd acpi code
> under /sys/contrib and keeping our local changes as patches, but
> maybe it's a bit too far.

After all, if I added the default rule and everything worked as expected.
I wrote another patch that put the build of acpi*.ko back into
/sys/dev/acpica5 as:
    http://les.ath.cx/DragonFly/acpi-update-2.patch.gz



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]