From owner-freebsd-ppc@FreeBSD.ORG Mon Dec 18 22:33:03 2006 Return-Path: X-Original-To: freebsd-ppc@freebsd.org Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0DC416A407; Mon, 18 Dec 2006 22:33:03 +0000 (UTC) (envelope-from andrew@fubar.geek.nz) Received: from fep04.xtra.co.nz (fep04.xtra.co.nz [210.54.141.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1831243CA3; Mon, 18 Dec 2006 22:33:02 +0000 (GMT) (envelope-from andrew@fubar.geek.nz) Received: from serv.int.fubar.geek.nz ([222.155.167.159]) by fep04.xtra.co.nz with ESMTP id <20061218223232.LLAV22675.fep04.xtra.co.nz@serv.int.fubar.geek.nz>; Tue, 19 Dec 2006 11:32:32 +1300 Date: Tue, 19 Dec 2006 11:32:30 +1300 From: Andrew Turner To: grehan@freebsd.org Message-ID: <20061219113230.34182787@hermies.int.fubar.geek.nz> In-Reply-To: <4586CA29.10803@freebsd.org> References: <20061218104841.72ba51ea@hermies.int.fubar.geek.nz> <4585CCC1.7050005@freebsd.org> <20061218222327.308dca53@hermies.int.fubar.geek.nz> <4586CA29.10803@freebsd.org> X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: FreeBSD on an Efika X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Dec 2006 22:33:03 -0000 On Mon, 18 Dec 2006 09:04:41 -0800 Peter Grehan wrote: > Hi Andrew, > > > I'm getting correct values from mem_regions. I can read from the > > physical address. > > What values are you getting back ? Does it look like what the > system should have ? For reg I'm getting the range 0x0 - 0x8000000. For available I'm getting the ranges 0x19111e4 - 0x02000000 and 0x24ff000 - 0x08000000. These are consistent with the values retrieved from the open firmware prompt. > Did you read as well as write the physical value ? Yes I can read and write to the physical address. > > > It is reading from msgbufp where it stop working. > > What're the virtual/physical values used when creating the msgbuf > mapping with pmap_kenter() in machdep.c:powerpc_init() ? The physical address is 0x1922000, the virtual address is 0xd0005000. > After that > mapping has been created, can you read/write to the buffer in that > routine ? Attempting to read or write to the value causes the kernel to stop. > Do you end up in the trap handler if you touch msgbuf ? Not as far as I can tell. > > pmap_kenter() is fundamental to the operation of the system and > probably OK, so something else must be afoot. > > later, > > Peter. > >