DragonFly commits List (threaded) for 2006-11
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Re: cvs commit: src/sys/cpu/i386/include float.h floatingpoint.h ieee.h ieeefp.h math.h perfmon.h profile.h setjmp.h sigframe.h sysarch.h tls.h varargs.h src/sys/ddb db_break.c src/sys/kern init_main.c kern_checkpoint.c kern_exec.c kern_exit.c kern_fp.c ...
On Wed, Nov 08, 2006 at 08:54:57AM -0800, Matthew Dillon wrote:
>
> :On Tue, Nov 07, 2006 at 09:51:24AM -0800, Matthew Dillon wrote:
> :> Log:
> :> Misc cleanups and CVS surgery. Move a number of header and source files
> :> from machine/pc32 to cpu/i386 as part of the ongoing architectural separation
> :> work and do a bit of cleanup.
> :
> :Is /sys/boot/i386/libi386 supposed to be removed, too?
>
> No, I'm trying to avoid messing with the boot build. At most we might
> rename it to sys/boot/pc32/libi386, but for now I'm just not worrying
> about it.
Well, my point was that I already saw the following two directories
/sys/boot/i386/libi386
/sys/boot/pc32/libi386
with almost the same contents, so I thought that you were planning to
remove one of them but didn't do it yet :)
So if my patch contained a patch to /sys/boot/i386/libi386/biosacpi.c,
I just need to change it to patch /sys/boot/pc32/libi386/biosacpi.c, right?
> The main thing is to separate cpu-specific components such as
> atomic.h, atomic.c, in_cksum2.s, from PC-specific components
> such as BIOS, ACPI, APM support, etc. Cpu components are being
> put in cpu/i386/... and PC components are being put in machine/pc32/...
>
> This way the virtual kernel build, which replaces the PC components,
> can still use the cpu components without having to duplicate them.
>
> -Matt
> Matthew Dillon
> <dillon@xxxxxxxxxxxxx>
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]