From: Finn Thain <fthain@telegraphics.com.au>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: 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: Sun, 15 Dec 2019 09:36:33 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.21.1.1912150919080.8@nippy.intranet> (raw)
In-Reply-To: <b95c70fe-aca0-faf7-4ff7-e71d8db3d149@physik.fu-berlin.de>
On Sat, 14 Dec 2019, John Paul Adrian Glaubitz wrote:
> Hi!
>
> When installing Debian/m68k inside qemu-m68k-system [1], we are
> currently limited to 1 GB of physical memory which is due to a limit in
> the Linux kernel as far as I know.
>
> However, I also know that it is possible to run the m68k kernel on
> Aranym with up to 3.5 GB of RAM. Thus, I was wondering whether there
> would be chance we could get the kernel patched to support more than 1
> GB of memory also on qemu-m68k-system which currently emulates an Apple
> Macintosh Quadra 800 system.
>
> Adrian
>
> > [1] https://wiki.debian.org/M68k/QemuSystemM68k
>
I believe that the reason for the limitation is the Mac memory map, as
Laurent pointed out in the issue tracker,
https://github.com/vivier/qemu-m68k/issues/42
It's theoretically possible to use NuBus slot space for additional RAM.
The super slot space ($6000 0000 thru $EFFF FFFF) is 2304 MB in size and
the standard slot space ($F100 0000 thru $FFFF FFFF) is another 239 MB.
I'm not sure about any hardware designs that took advantage of this
possibility (Radius Rocket perhaps?).
--
next prev parent reply other threads:[~2019-12-14 22:36 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 [this message]
2019-12-15 1:41 ` Brad Boyer
2019-12-15 11:01 ` Geert Uytterhoeven
2019-12-17 0:26 ` Finn Thain
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.1912150919080.8@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=debian-68k@lists.debian.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).