From owner-freebsd-arch@FreeBSD.ORG Thu Nov 4 23:17:30 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E01B16A4CF; Thu, 4 Nov 2004 23:17:30 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 834A343D2F; Thu, 4 Nov 2004 23:17:29 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual.digiware.nl [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id iA4NHS5p006393; Fri, 5 Nov 2004 00:17:28 +0100 (CET) (envelope-from wjw@withagen.nl) Message-ID: <418AB888.7070305@withagen.nl> Date: Fri, 05 Nov 2004 00:17:28 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <418AB176.9030604@withagen.nl> <418AB649.80809@freebsd.org> In-Reply-To: <418AB649.80809@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: "arch@freebsd.org" Subject: Re: Booting questions .... X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 23:17:30 -0000 Scott Long wrote: > The loader has a protected mode environment. It is apparently not all > that hard to port memtest86 into it. I'd highly recommend doing this > rather than trying to hack up the early pmap initialization. Is that so.... I was unable to find that. :( can you give me a pointer?? And like I wrote in the previous discussion. The algorithms are not all that difficult to write. It is getting easy access to the memory. If you look at memtest86, you'll that they have to get a lot of work done to get to the actual job: memory testing. And that only for the x86 type processors, which are already served by memtest86. But reading your question, the answer would be: too complex to get this figured out Then how about this: what minimal parts of the kernel do I need to get at least: 1 cpu booted flat memoryspace printf working on the console (vga of serial) areas which are taken by the above. do I again get into pmap init stuff. --WjW