[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdXWfLa8dCZPF6jSQYuowGBR4dJnS1hx_rN1kDpPFZnVGg@mail.gmail.com>
Date: Wed, 26 Aug 2020 13:28:48 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
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 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.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists