Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 Aug 2004 16:38:01 +0100
From:      Mark Murray <mark@grondar.org>
To:        des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=)
Cc:        cvs-all@FreeBSD.ORG
Subject:   Re: cvs commit: src/sys/alpha/alpha mem.c src/sys/alpha/conf GENERIC src/sys/alpha/include memdev.h src/sys/amd64/amd64 io.c mem.c src/sys/amd64/conf GENERIC NOTES src/sys/amd64/include iodev.h memdev.h src/sys/conf NOTES files files.alpha files.amd64 ... 
Message-ID:  <200408021538.i72Fc1fa026647@grimreaper.grondar.org>
In-Reply-To: Your message of "Mon, 02 Aug 2004 17:17:57 %2B0200." <xzpoelt8t7e.fsf@dwp.des.no> 

next in thread | previous in thread | raw e-mail | index | archive | help
=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= writes:
> Mark Murray <markm@FreeBSD.org> writes:
> >   Log:
> >   Break out the MI part of the /dev/[k]mem and /dev/io drivers into
> >   their own directory and module, leaving the MD parts in the MD
> >   area (the MD parts _are_ part of the modules). /dev/mem and /dev/io
> >   are now loadable modules, thus taking us one step further towards
> >   a kernel created entirely out of modules. Of course, there is nothing
> >   preventing the kernel from having these statically compiled.
> 
> OK, there's one problem with this commit: mem_range_AP_init() is
> defined in mem.c, but referenced in mp_machdep.c (and nowhere else).
> Therefore, you can't build an i386 or amd64 SMP kernel without 'device
> mem'.  I believe that simply moving mem_range_AP_init() to a different
> file (perhaps machdep.c?) should fix this.

Untangling this will take a while. The softc needs to move as well.

M
--
Mark Murray
iumop ap!sdn w,I idlaH



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408021538.i72Fc1fa026647>