From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J1Y4m-0003tG-4O for qemu-devel@nongnu.org; Sun, 09 Dec 2007 21:08:56 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J1Y4k-0003ri-Sg for qemu-devel@nongnu.org; Sun, 09 Dec 2007 21:08:55 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J1Y4k-0003rf-MV for qemu-devel@nongnu.org; Sun, 09 Dec 2007 21:08:54 -0500 Received: from gateway-1237.mvista.com ([63.81.120.158]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J1Y4k-00070A-2p for qemu-devel@nongnu.org; Sun, 09 Dec 2007 21:08:54 -0500 Received: from pahoa.hi.kama-aina.net (unknown [10.235.20.2]) by hermes.mvista.com (Postfix) with ESMTP id 178441EC70 for ; Sun, 9 Dec 2007 18:08:51 -0800 (PST) Message-ID: <475C9FB2.8010601@kama-aina.net> Date: Sun, 09 Dec 2007 16:08:50 -1000 From: Armin MIME-Version: 1.0 Subject: Re: [Qemu-devel] [Patch][update] Mainstone re-org plus flash References: <474B89C0.2050007@kama-aina.net> <20071202045518.GB617@networkno.de> <4753355C.1030003@kama-aina.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org andrzej zaborowski wrote: > On 10/12/2007, andrzej zaborowski wrote: > >> On 02/12/2007, Armin wrote: >> >>> Thiemo, >>> >>> Thiemo Seufer wrote: >>> >>>> Armin wrote: >>>> >>>> >>>>> Hello, >>>>> >>>>> This includes the previous Mainstone re-org patch I sent earlier plus flash >>>>> support. >>>>> This adds two 32MiB flash devices. Mounts from mtdblock2 on flash device 0 >>>>> fine at boot. >>>>> >>>>> >>>> I did some guesswork on the flash initialization to make it build with >>>> Laurent's -disk patch. Please check if it is still correct. >>>> >>>> >>> works fine. >>> >> Note that both chips get mapped at the same offset in phys_ram_base, >> I'm quite sure this is a bug and not intentional? It may corrupt data >> if the OS reads from both chips. I wanted to convert mainstone.c to >> use qemu_ram_alloc like other pxa boards but I want to make sure this >> is not intentional. >> >> The value of mainstone_rom indicates this too. >> > > Sorry, mainstone_rom is not related to this issue, but that means that > the ram_size check allows too low values and qemu may crash. It also > means that the two flash chips *and* the ROM all overlap. I think > gumstix.c registers the flash correctly, you may wnat to look in it. > Regards > will do. I seem to remember that the two mappings are mutually exclusive and possible controlled by an external switch.. I will need to double check that. sorry for the trouble. -Armin