From: Chris Brandt <Chris.Brandt@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Nicolas Pitre <nico@fluxnic.net>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH/RFC] ARM: dts: rza2mevb: Upstream Linux requires SDRAM
Date: Fri, 8 May 2020 14:05:31 +0000 [thread overview]
Message-ID: <OSAPR01MB2114FB6F10EC904F19363F9D8AA20@OSAPR01MB2114.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdW0=KWk2pC2tRUajvZQsoObBEFz7WoJ+uJbHbX27f7b2g@mail.gmail.com>
Hi Geert and Nicolas,
On Fri, May 8, 2020, Geert Uytterhoeven wrote:
> Do you have any guidance how to implement that?
> So far our tries have failed.
Ahh....A nice history of my failed attempts :o
The big argument was always that "XIP cannot be multi-platform by
definition because RAM/ROM always resides at different addresses in different
devices". And as you know, the physical address for RAM and ROM have to
be hard coded in the kernel binary.
At an ELC a while back, I talked to Arnd and his suggestion was to put
the base addresses for RAM and ROM at a fixed location in the kernel
binary. Then for each SoC, you manually modify those values in the each
binary to match your board. This means there is 'technically' a single build
that will support all boards.
I admit, while it sounded reasonable, I never tried it. Mostly because
it seemed like a lot of work just to send a patch that might get
instantly NAK-ed.
Chris
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-08 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 8:05 [PATCH/RFC] ARM: dts: rza2mevb: Upstream Linux requires SDRAM Geert Uytterhoeven
2020-05-07 14:58 ` Nicolas Pitre
2020-05-07 16:08 ` Geert Uytterhoeven
2020-05-07 17:06 ` Nicolas Pitre
2020-05-08 13:38 ` Geert Uytterhoeven
2020-05-08 14:05 ` Chris Brandt [this message]
2020-05-08 14:41 ` Nicolas Pitre
2020-05-08 15:56 ` Geert Uytterhoeven
2020-05-08 16:15 ` Nicolas Pitre
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=OSAPR01MB2114FB6F10EC904F19363F9D8AA20@OSAPR01MB2114.jpnprd01.prod.outlook.com \
--to=chris.brandt@renesas.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=nico@fluxnic.net \
/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).