Date: Fri, 21 Jul 2006 16:40:47 -0700 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Alan Cox <alc@cs.rice.edu> Cc: cvs-src@FreeBSD.ORG, src-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, "M. Warner Losh" <imp@bsdimp.com> Subject: Re: cvs commit: src/share/mk bsd.cpu.mk Message-ID: <20060721234047.GA14618@dragon.NUXI.org> In-Reply-To: <44C11E6C.3070302@cs.rice.edu> References: <200607202242.k6KMgmQq064714@repoman.freebsd.org> <44C012D1.2050905@cs.rice.edu> <20060720.173927.790476985.imp@bsdimp.com> <20060721125118.GA6326@dragon.NUXI.org> <44C11E6C.3070302@cs.rice.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 21, 2006 at 01:35:24PM -0500, Alan Cox wrote: > >Alan I'm curious, for you what is the rush? > > It complicates my efforts to maintain and improve the virtual memory > system when I can only compile-test changes on five out of the six > architectures in CVS without jumping through hoops. In other words, the > lack of a tool-chain in CVS is becoming a drag, not just on those with > particular interest in arm, but the project as a whole. For example. > after consulting with grehan@ and marcel@, I decided that the best way > to finish the PG_NX support on amd64 involved a pmap interface change, > which means changing the arm pmap as well as the five that compile > out-of-the-box. Thanks for the replay, I just wondered if there was a special need for your VM, etc. work. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060721234047.GA14618>