From: Kars de Jong <jongk@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] m68k: fix for systems with memory at end of 32-bit address space
Date: Fri, 24 Feb 2023 11:40:53 +0100 [thread overview]
Message-ID: <CACz-3rh+m7FEXVyNUUwCzbUFg6Ytk-iMNcc12o_WNie69aHT+Q@mail.gmail.com> (raw)
In-Reply-To: <CACz-3rhNFb81+auU10+ctG2XrcvKgQ7o0MGy+6DV5MsNw9XmNg@mail.gmail.com>
Op do 23 feb. 2023 om 15:05 schreef Kars de Jong <jongk@linux-m68k.org>:
>
> Op do 23 feb. 2023 om 13:39 schreef Geert Uytterhoeven <geert@linux-m68k.org>:
> >
> > So this has been broken for the last 15 years?
>
> Yes, looks like this commit broke it:
> https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git/commit/arch/m68k/mm/motorola.c?id=12d810c1b8c2b913d48e629e2b5c01d105029839,
> so slightly longer than 15 years :-).
I found the original thread where I reported this here:
https://marc.info/?t=117175647600006&r=1&w=2, including a version of
this same patch, created by Roman Zippel:
https://marc.info/?l=linux-m68k&m=117184910524555&w=2. This was still
in CVS times.
Apparently I used to work around this issue by subtracting 1 from the
memory size in my boot loader.
Now I just need to figure out why the last page of memory is excluded.
Do you also see this on other machines?
Zone ranges:
DMA [mem 0x00000000fc000000-0x00000fffffffefff]
Normal empty
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x00000000fc000000-0x00000000ffffefff]
Initmem setup node 0 [mem 0x00000000fc000000-0x00000000ffffefff]
Kind regards,
Kars.
next prev parent reply other threads:[~2023-02-24 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 11:23 [PATCH] m68k: fix for systems with memory at end of 32-bit address space Kars de Jong
2023-02-23 12:39 ` Geert Uytterhoeven
2023-02-23 14:05 ` Kars de Jong
2023-02-24 10:40 ` Kars de Jong [this message]
2023-02-24 11:01 ` Geert Uytterhoeven
2023-02-24 18:57 ` Michael Schmitz
2023-02-23 14:29 ` Kars de Jong
2023-03-06 12:56 ` Geert Uytterhoeven
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=CACz-3rh+m7FEXVyNUUwCzbUFg6Ytk-iMNcc12o_WNie69aHT+Q@mail.gmail.com \
--to=jongk@linux-m68k.org \
--cc=geert@linux-m68k.org \
--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).