From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Arnd Bergmann <arnd@arndb.de>, Jason Gunthorpe <jgg@nvidia.com>
Cc: ksummit@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, linux-mips@vger.kernel.org,
linux-mm@kvack.org, imx@lists.linux.dev,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Richard Weinberger" <richard@nod.at>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Ankur Arora" <ankur.a.arora@oracle.com>,
"David Hildenbrand" <david@redhat.com>,
"Mike Rapoport" <rppt@kernel.org>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Suren Baghdasaryan" <surenb@google.com>,
"Ira Weiny" <ira.weiny@intel.com>, "Nishanth Menon" <nm@ti.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Alexander Sverdlin" <alexander.sverdlin@gmail.com>,
"Chester A. Unal" <chester.a.unal@arinc9.com>,
"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
"Andreas Larsson" <andreas@gaisler.com>
Subject: Re: [TECH TOPIC] Reaching consensus on CONFIG_HIGHMEM phaseout
Date: Fri, 19 Sep 2025 16:22:10 +0200 [thread overview]
Message-ID: <775e175a-6699-4b7b-a997-3d142fdf64e4@microchip.com> (raw)
In-Reply-To: <02b0f383-1c43-4eeb-a76f-830c2970b833@app.fastmail.com>
On 18/09/2025 at 15:12, Arnd Bergmann wrote:
> * Microchip SAM9x7 is the newest ARMv5 chip, clearly does
> get kernel updates, and the only one I can think of with
> DDR3 support, but seems to be limited to 256MB total memory.
It is indeed.
No difficulty on this part of the product line ;-)
Best regards,
Nicolas
prev parent reply other threads:[~2025-09-19 14:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 21:23 [TECH TOPIC] Reaching consensus on CONFIG_HIGHMEM phaseout Arnd Bergmann
2025-09-09 21:38 ` H. Peter Anvin
2025-09-09 22:24 ` Linus Torvalds
2025-09-09 22:39 ` H. Peter Anvin
2025-09-10 1:06 ` René Herman
2025-09-10 1:46 ` Matthew Wilcox
2025-09-10 9:49 ` Linus Walleij
2025-09-10 12:17 ` Arnd Bergmann
2025-09-10 12:32 ` David Hildenbrand
2025-09-10 13:10 ` Linus Walleij
2025-09-10 14:04 ` Matthew Wilcox
2025-09-10 15:13 ` Arnd Bergmann
2025-09-10 14:04 ` Richard Weinberger
2025-09-10 16:34 ` Dave Hansen
2025-09-10 20:33 ` Richard Weinberger
2025-09-10 21:56 ` René Herman
2025-09-12 10:30 ` Arnd Bergmann
2025-09-12 12:46 ` Linus Walleij
2025-10-06 20:15 ` Richard Weinberger
2025-09-10 17:11 ` Christophe Leroy
2025-09-10 19:37 ` Richard Weinberger
2025-09-11 5:38 ` Andreas Larsson
2025-09-11 7:53 ` Arnd Bergmann
2025-09-12 9:32 ` Andreas Larsson
2025-09-12 9:36 ` H. Peter Anvin
2025-09-12 10:17 ` Arnd Bergmann
2025-09-12 9:58 ` H. Peter Anvin
2025-09-12 13:16 ` Matthew Wilcox
2025-09-12 16:49 ` Nicolas Ferre
2025-09-12 21:09 ` Arnd Bergmann
2025-09-17 12:59 ` Jason Gunthorpe
2025-09-18 13:12 ` Arnd Bergmann
2025-09-18 13:34 ` Andrew Lunn
2025-09-18 16:18 ` Arnd Bergmann
2025-09-18 16:32 ` Andrew Lunn
2025-09-19 7:17 ` Geert Uytterhoeven
2025-09-19 14:22 ` Arnd Bergmann
2025-09-19 14:34 ` Jason Gunthorpe
2025-09-22 6:58 ` Arnd Bergmann
2025-09-22 17:05 ` Nicolas Schichan
2025-09-22 21:22 ` Arnd Bergmann
2025-09-19 14:41 ` Nicolas Ferre
2025-09-19 14:22 ` Nicolas Ferre [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=775e175a-6699-4b7b-a997-3d142fdf64e4@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.sverdlin@gmail.com \
--cc=andreas@gaisler.com \
--cc=ankur.a.arora@oracle.com \
--cc=arnd@arndb.de \
--cc=chester.a.unal@arinc9.com \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=geert+renesas@glider.be \
--cc=heiko@sntech.de \
--cc=imx@lists.linux.dev \
--cc=ira.weiny@intel.com \
--cc=jgg@nvidia.com \
--cc=ksummit@lists.linux.dev \
--cc=l.stach@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=nm@ti.com \
--cc=richard@nod.at \
--cc=rppt@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.