From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Brad Boyer <flar@allandria.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
Debian m68k <debian-68k@lists.debian.org>
Subject: Re: Using more than 1 GB in qemu-m68k-system
Date: Tue, 17 Dec 2019 11:26:09 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.21.1.1912171054150.11@nippy.intranet> (raw)
In-Reply-To: <CAMuHMdW26v_j=ADaisMN-FqC2v+YYRs3W0J0jy2+sgO_YCxYOw@mail.gmail.com>
On Sun, 15 Dec 2019, Geert Uytterhoeven wrote:
> Hi Brad,
>
> On Sun, Dec 15, 2019 at 3:19 AM Brad Boyer <flar@allandria.com> wrote:
> > We could probably emulate a fake NuBus card in qemu that is just
> > memory in the super slot space for that card. Can a regular driver add
> > RAM, or would we have to detect that in the core code somewhere?
>
> I think a regular driver can do that, if CONFIG_MEMORY_HOTPLUG=y.
> However, the latter depends on CONFIG_SPARSEMEM.
>
> The early core code can just call memblock_add(), though.
>
The nubus subsystem isn't available during early boot. The regular driver
option might be the best option.
BTW, the Nubus memory mapping done in arch/m68k/kernel/head.S (0xf8000000
through 0xffffffff) covers the standard slot space but not the super slot
space.
> Gr{oetje,eeting}s,
>
> Geert
>
>
prev parent reply other threads:[~2019-12-17 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 20:20 Using more than 1 GB in qemu-m68k-system John Paul Adrian Glaubitz
2019-12-14 22:36 ` Finn Thain
2019-12-15 1:41 ` Brad Boyer
2019-12-15 11:01 ` Geert Uytterhoeven
2019-12-17 0:26 ` Finn Thain [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=alpine.LNX.2.21.1.1912171054150.11@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=debian-68k@lists.debian.org \
--cc=flar@allandria.com \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@lists.linux-m68k.org \
/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;
as well as URLs for NNTP newsgroup(s).