From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Hourihane Subject: Re: Atari TT (next) Date: Sun, 08 Jan 2012 23:49:31 +0000 Message-ID: <4F0A2B8B.5060802@fairlite.co.uk> References: <4F079F6B.8080502@fairlite.co.uk> <4F07EA66.6020603@gmail.com> <4F08E748.4020305@fairlite.co.uk> <4F0917E9.9090600@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from fairlite.demon.co.uk ([80.176.228.186]:56035 "EHLO fairlite.demon.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754748Ab2AHXtj (ORCPT ); Sun, 8 Jan 2012 18:49:39 -0500 In-Reply-To: Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Michael Schmitz Cc: Andreas Schwab , Geert Uytterhoeven , Linux/m68k On 08/01/12 23:39, Michael Schmitz wrote: > Hi Andreas, > >>> support. Is there a strict requirement (from the kernel's early >>> startup and mem_init POV) that the kernel has to reside in the first >>> bootinfo memory chunk? >> It is a requirement that the kernel is mapped at virtual address zero >> since it is not relocatable. > That much I understand - but can we tweak the bootinfo to report the > chunks in physical address order? What I mean to say is - does the > first bootinfo chunk get mapped at virtual address zero always, or is > there some check to see what physical address corresponds to the > kernel segment? > >>From what I can see the first mem_info struct is always mapped at VA 0 which is done in paging_init() in mm/motorola.c Alan.