[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8a94e52c-4b29-5013-3ea4-af4223abda46@physik.fu-berlin.de>
Date: Wed, 26 Aug 2020 13:34:01 +0200
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>,
Stefan Reinauer <stefan.k.reinauer@...il.com>,
linux-m68k <linux-m68k@...ts.linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] zorro: Fix address space collision message with RAM
expansion boards
On 8/26/20 1:28 PM, Geert Uytterhoeven wrote:
> On Mon, Jul 13, 2020 at 9:24 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>> When booting Linux on an Amiga with BigRAMPlus Zorro expansion board:
>>
>> zorro: Address space collision on device Zorro device 12128600 (Individual Computers) [??? 0x50000000-]
>>
>> This happens because the address space occupied by the BigRAMPlus Zorro
>> device is already in use, as it is part of system RAM. Hence the
>> message is harmless.
>>
>> Zorro memory expansion boards have the ERTF_MEMLIST flag set, which
>> tells AmigaOS to link the board's RAM into the free memory list. While
>> we could skip registering the board resource if this flag is set, that
>> may cause issues with Zorro II RAM excluded in a memfile.
>>
>> Hence fix the issue by just ignoring the error if ERTF_MEMLIST is set.
>>
>> Reported-by: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
>> Signed-off-by: Geert Uytterhoeven <geert@...ux-m68k.org>
>
> Applied, and queued in the m68k for-v5.10 branch.
Oh, that reminds me. I should dig out the Big-RAM-Plus again. I still haven't
found it after my last move but I know where to find it (hopefully ;-)).
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@...ian.org
`. `' Freie Universitaet Berlin - glaubitz@...sik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists