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 ...

[David O'Brien]

On Mon, Aug 02, 2004 at 04:38:01PM +0100, Mark Murray wrote:
> =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= writes:
> > Mark Murray <markm at 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.

Was your /dev/mem as-a-module commit tested?  Since I and others can't
build a kernel without "device mem" I don't see how this could be tested.

-- 
-- David  (obrien at FreeBSD.org)