diff options
| author | Geert Uytterhoeven <geert@linux-m68k.org> | 2020-07-13 09:24:29 +0200 |
|---|---|---|
| committer | Geert Uytterhoeven <geert@linux-m68k.org> | 2020-08-26 13:26:52 +0200 |
| commit | ea2abe2fd59a73b26c01e9a3bb83efc46e44face (patch) | |
| tree | 96c6aa36ec448c0dfb7067316eb6084ab608ef56 /drivers/zorro | |
| parent | 3b0950af21e02a8c902ce1143ac5563fadcdfb3e (diff) | |
| download | linux-ea2abe2fd59a73b26c01e9a3bb83efc46e44face.tar.bz2 | |
zorro: Fix address space collision message with RAM expansion boards
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>
Link: https://lore.kernel.org/r/20200713072429.6182-1-geert@linux-m68k.org
Diffstat (limited to 'drivers/zorro')
| -rw-r--r-- | drivers/zorro/zorro.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/zorro/zorro.c b/drivers/zorro/zorro.c index 47c733817903..1b9928648583 100644 --- a/drivers/zorro/zorro.c +++ b/drivers/zorro/zorro.c @@ -181,7 +181,7 @@ static int __init amiga_zorro_probe(struct platform_device *pdev) z->resource.name = z->name; r = zorro_find_parent_resource(pdev, z); error = request_resource(r, &z->resource); - if (error) + if (error && !(z->rom.er_Type & ERTF_MEMLIST)) dev_err(&bus->dev, "Address space collision on device %s %pR\n", z->name, &z->resource); |