Date: Mon, 2 Aug 2004 09:15:27 -0700 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Mark Murray <mark@grondar.org> Cc: cvs-src@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: <20040802161527.GA96135@dragon.nuxi.com> In-Reply-To: <200408021538.i72Fc1fa026647@grimreaper.grondar.org> References: <xzpoelt8t7e.fsf@dwp.des.no> <200408021538.i72Fc1fa026647@grimreaper.grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040802161527.GA96135>