From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells In-Reply-To: <20090416151433.GS1760@mail.wantstofly.org> References: <20090416151433.GS1760@mail.wantstofly.org> <20090416150630.GR1760@mail.wantstofly.org> <5680.1239894019@redhat.com> <11416.1239894581@redhat.com> To: Lennert Buytenhek Subject: Re: Bug in physmap driver? Date: Thu, 16 Apr 2009 16:27:44 +0100 Message-ID: <13360.1239895664@redhat.com> Sender: dhowells@redhat.com Cc: dhowells@redhat.com, linux-mtd@lists.infradead.org, David Woodhouse List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Lennert Buytenhek wrote: > The last useful address. That's what the resource code expects, as > e.g. two regions with start=00100000,end=00200000 and > start=00200000,end=00300000 will conflict (registration of the second > will fail), whereas if you change the end addresses to 001fffff and > 002fffff, they will no longer conflict. Okay, yes; you're right. It no longer locks up. Do you by any chance know what the 'width' field of struct physmap_flash_data means? Is it the total width of the data bus going to the flash chips? Or is it the width of each flash chip? David