Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Imre Kaloz <kaloz@kernel.org>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] MIPS: sgi-ip32: Reserve the firmware memory
Date: Tue, 17 Nov 2026 17:56:14 +0100	[thread overview]
Message-ID: <avyHLu4-jaWCSuut@alpha.franken.de> (raw)
In-Reply-To: <20261013094554.16804-3-kaloz@kernel.org>

On Tue, Oct 13, 2026 at 11:45:53AM +0200, Imre Kaloz wrote:
> ARC memory descriptors are ignored on IP32, so firmware data in low
> memory ends up in the page allocator and CMA. Reserve it using the
> generic ARC walk; RAM comes from CRIME, as ARC lists only the first
> 256 MiB.
> 
> Signed-off-by: Imre Kaloz <kaloz@kernel.org>
> ---
>  arch/mips/fw/arc/memory.c        | 11 +++++++++--
>  arch/mips/include/asm/sgialib.h  |  3 +++
>  arch/mips/sgi-ip32/ip32-memory.c |  3 +++
>  3 files changed, 15 insertions(+), 2 deletions(-)

applied to mips-next

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2026-11-17 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  9:45 [PATCH 0/3] MIPS: SGI fixes Imre Kaloz
2026-10-13  9:45 ` [PATCH 1/3] MIPS: sgi-ip32: Clear latched CRIME errors at boot Imre Kaloz
2026-11-17 16:55   ` Thomas Bogendoerfer
2026-10-13  9:45 ` [PATCH 2/3] MIPS: sgi-ip32: Reserve the firmware memory Imre Kaloz
2026-11-17 16:56   ` Thomas Bogendoerfer [this message]
2026-10-13  9:45 ` [PATCH 3/3] MIPS: SGI-IP30: fix the defconfig defaults for the Bridge PROM and RTC Imre Kaloz
2026-11-05 15:22   ` Thomas Bogendoerfer

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=avyHLu4-jaWCSuut@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=kaloz@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.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