linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: XIP_KERNEL and !ARCH_MULTIPLATFORM
Date: Fri, 20 Mar 2015 08:19:10 +0000	[thread overview]
Message-ID: <20150320081910.GF10068@pengutronix.de> (raw)
In-Reply-To: <HK2PR06MB05611C6D6CED1E32F4617D158A010@HK2PR06MB0561.apcprd06.prod.outlook.com>

On Thu, Mar 19, 2015 at 08:57:21PM +0000, Chris Brandt wrote:
> Eventually....I got it to boot.
> 
> I had to remove both CONFIG_HIGHMEM and CONFIG_SMP and then I could boot completely from ROM (which for me is external QSPI flash that is memory mapping into linear CPU space at address 0x18000000)
> 
> So, the total changes was:
> 
> 1. start with shmobile_defconfig
> 2. remove all architectures but RZ/A1 (ARCH_R7S72100)
> 3. remove !ARCH_MULTIPLATFORM from XIP_KERNEL's dependencies
> 4. modify  'select ARM_PATCH_PHYS_VIRT if !XIP_KERNEL'  in PHYS_OFFSET (because I need to be able to set PHYS_OFFSET)
> 5. patch up mmu.c, proc-v7.S and link-vmlinux.sh
> 6. remove CONFIG_HIGHMEM and CONFIG_SMP
> 
> I also modified the DT to use internal RAM instead external SDRAM.
> 
> Of course to actually boot an XIP kernel, you have to make a custom command in u-boot (using bootm or go is not going to work).
It should. I remember that you need to pass something unintuitive to
mkimage (to not say buggy). See
http://lists.denx.de/pipermail/u-boot/2007-March/020171.html for my try
to fix that back when I still cared about U-Boot.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2015-03-20  8:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17  3:48 XIP_KERNEL and !ARCH_MULTIPLATFORM Chris Brandt
2015-03-17 10:26 ` Russell King - ARM Linux
2015-03-17 13:29   ` Chris Brandt
2015-03-17 10:50 ` Geert Uytterhoeven
2015-03-17 13:46   ` Chris Brandt
2015-03-17 13:57     ` Geert Uytterhoeven
2015-03-17 16:08       ` Chris Brandt
2015-03-17 16:20         ` Geert Uytterhoeven
2015-03-17 16:28           ` Russell King - ARM Linux
2015-03-17 16:37             ` Chris Brandt
2015-03-17 16:34           ` Chris Brandt
2015-03-19 20:57           ` Chris Brandt
2015-03-20  8:19             ` Uwe Kleine-König [this message]
2015-03-20 20:18               ` Chris Brandt
2015-03-22  9:13                 ` Uwe Kleine-König
2015-03-20 22:23             ` Russell King - ARM Linux
2015-03-21 15:39               ` Chris Brandt
2015-03-22 16:57                 ` Russell King - ARM Linux
2015-03-22 19:48                   ` Arnd Bergmann
2015-03-23  1:41                     ` Chris Brandt
2015-03-23  1:24                   ` Chris Brandt
2015-03-23  5:54                     ` Arnd Bergmann
2015-03-23 13:54                       ` Chris Brandt
2015-03-22 19:40                 ` Arnd Bergmann
2015-03-23  1:37                 ` Geert Uytterhoeven
2015-03-23  1:49                   ` Chris Brandt
2015-03-17 16:36 ` Uwe Kleine-König
2015-04-05 16:02 ` Russell King - ARM Linux
2015-04-07  3:31   ` Chris Brandt

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=20150320081910.GF10068@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.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 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).