From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Stefan Reinauer <stefan.k.reinauer@gmail.com>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] zorro: Fix address space collision message with RAM expansion boards
Date: Wed, 26 Aug 2020 13:34:01 +0200 [thread overview]
Message-ID: <8a94e52c-4b29-5013-3ea4-af4223abda46@physik.fu-berlin.de> (raw)
In-Reply-To: <CAMuHMdXWfLa8dCZPF6jSQYuowGBR4dJnS1hx_rN1kDpPFZnVGg@mail.gmail.com>
On 8/26/20 1:28 PM, Geert Uytterhoeven wrote:
> On Mon, Jul 13, 2020 at 9:24 AM Geert Uytterhoeven <geert@linux-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@physik.fu-berlin.de>
>> Signed-off-by: Geert Uytterhoeven <geert@linux-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@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2020-08-26 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 7:24 Geert Uytterhoeven
2020-08-26 11:28 ` Geert Uytterhoeven
2020-08-26 11:34 ` John Paul Adrian Glaubitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a94e52c-4b29-5013-3ea4-af4223abda46@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=stefan.k.reinauer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®