Received: by 2002:a05:6a10:6006:0:0:0:0 with SMTP id w6csp46959pxa; Wed, 26 Aug 2020 04:31:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyZk515FqHdtqx9FofNzqTyLiB4sY9iyXCU+K1FtylAsB1EzFxqLrTX8aj6D+qY9Zld0zfD X-Received: by 2002:a17:906:b896:: with SMTP id hb22mr7481431ejb.351.1598441514369; Wed, 26 Aug 2020 04:31:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598441514; cv=none; d=google.com; s=arc-20160816; b=WXusju18z3zdV9io7kGVmtCnoiX+Aav9Q4M4JwyyVMc4e+KCbY0mFzjmRCfdhMfQPa oqeCP10dwGCUTrthVQszfOJorP/jBX5hcFvUbOorLpe1tjkeWd5eyJag5wwKMLuJq7Ey 30BaNHiuCh3JQcPIavVJr9XKwcpA/otM/yRQJU5oAtFWAQZ/hJ1QXp6M4rujWH42wSJ+ QuB4HHzQ7hwNkurqkZ/g462vM/yPl2Ks8S29Xmb74Rv+qrk70DSW31YlFb13+BQH37KI 2OoDXWpZMxKht+hGqCh5f+ROzn/NulDwvoRLOM14F0y/Vgd0tG5wc/DyRmaftIlvBVbk MGAw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=1FLY0eW4GFuoR8mTu1lJlREb+UEGmC42E+5Rra5UznE=; b=M1uyOcCNUDsW0eFbMr6AVBHKkEwPUPDXerqC4qjP+IZdYsS8iHV1pRLpwZlj8v5RLk C9wDu8biB8eKOIRGbgemXsq/RHr5zNigN25+byYxc8ef9auv5eoCDu8DDYoTWyj+JfMW dLJpvMhwf6mD44C7tY2kII28xekLLibL7mDAPABm+Mo1rJTErerkgudK1oymP+IPQWnI yDKfsizB3qoTSCAeeY9Kd2+5m0FVtnST0hHtXUI2zSRQN885GPuyuPvbeDXcwy5VDaGb 8kg5gaVZX6bgsR9qjkk86a2fx341xT/GS6xf6HgO4jKOy+K15ms/Lf/uPMYQm5KCKGkj CwcA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bx1si1407676ejb.370.2020.08.26.04.31.30; Wed, 26 Aug 2020 04:31:54 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728963AbgHZLaN (ORCPT + 99 others); Wed, 26 Aug 2020 07:30:13 -0400 Received: from mail-oi1-f194.google.com ([209.85.167.194]:43880 "EHLO mail-oi1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728937AbgHZL3X (ORCPT ); Wed, 26 Aug 2020 07:29:23 -0400 Received: by mail-oi1-f194.google.com with SMTP id j21so1178847oii.10 for ; Wed, 26 Aug 2020 04:29:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1FLY0eW4GFuoR8mTu1lJlREb+UEGmC42E+5Rra5UznE=; b=XU0hHOssQQ1fWDN//FfT7reueVj+pS4F1dFxIdtsvGFou3Ud5xpIx17zuyVUCVFB94 x3DJDEt8+noMnYXiDBiX7sQyrrYZkIQiTRMBSZm7Lsfhy47AWJBnVkGPUsZWEyILOb73 gnrls34xQ9zunoUHV8rRfwApALE4iJwa7gD7zEIC6MKaM9L4KOQ/rendmMeDmTkYaXbd tE6TycpClPloiIJl8J+thvixNf8TMHcZNkirteuYUMqe+CuqokAE0Dy7QJ9+fwumYhXf QpD8GKP+GYgBYdspBmVStgHK1jTn7wj8quuWMkan1UfiTD8GagtagVgsyjnC/e2Qv2WF D74w== X-Gm-Message-State: AOAM530QzcvyciHgDxZOjw7U327f+UuRZDqkRV1jZoZIJHpCMl5KgKkZ mBW2jWfRV6jakKOI6vOnntla5JjK8I0clWrdqcM= X-Received: by 2002:aca:b742:: with SMTP id h63mr3423281oif.148.1598441339761; Wed, 26 Aug 2020 04:28:59 -0700 (PDT) MIME-Version: 1.0 References: <20200713072429.6182-1-geert@linux-m68k.org> In-Reply-To: <20200713072429.6182-1-geert@linux-m68k.org> From: Geert Uytterhoeven Date: Wed, 26 Aug 2020 13:28:48 +0200 Message-ID: Subject: Re: [PATCH] zorro: Fix address space collision message with RAM expansion boards To: John Paul Adrian Glaubitz , Stefan Reinauer , linux-m68k Cc: Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 13, 2020 at 9:24 AM Geert Uytterhoeven 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 > Signed-off-by: Geert Uytterhoeven 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@linux-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