linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: new platform for Energy Micro's EFM32 Cortex-M3 SoCs
Date: Mon, 30 Sep 2013 17:49:12 +0200	[thread overview]
Message-ID: <20130930154912.GE2548@pengutronix.de> (raw)
In-Reply-To: <201309292100.41701.arnd@arndb.de>

Hello Arnd,

On Sun, Sep 29, 2013 at 09:00:41PM +0200, Arnd Bergmann wrote:
> On Saturday 28 September 2013, Uwe Kleine-K?nig wrote:
> > On Fri, Sep 27, 2013 at 11:44:01PM +0200, Arnd Bergmann wrote:
> > > On Thursday 26 September 2013, Uwe Kleine-K?nig wrote:
> > > > I made that work now and can prepare a patch. I had to drop "depends on
> > > > !ARCH_MULTIPLATFORM" from XIP_KERNEL. That's because my machine only
> > > > works with XIP_KERNEL as it only has 4 MiB of RAM.
> > > 
> > > Ok, cool. We might run into a few problems with 'make randconfig' and
> > > 'make allyesconfig' when it becomes possible to enable XIP_KERNEL then.
> > > IIRC, there is no fundamental reason to disallow XIP_KERNEL with
> > > ARCH_MULTIPLATFORM, but I added the dependency because it causes
> > > build errors in combination with other options.
> > ah, OK. Do you have an idea to fix both?
> 
> No, I don't actually remember what problems I ran into. It may be anywhere
> from trivial to impossible to fix.
I sent a patch series (without looking much for problems :-).

> > There is a BSP publically available at
> > 
> > 	http://git-public.pengutronix.de/?p=OSELAS.BSP-EnergyMicro-Gecko.git;a=summary
> > 
> > which also includes a README file. For troubleshooting /join #efm32 on
> > freenode.
> 
> I've never tried ptxdist, but if that is known to work fine with NOMMU,
> I might just try building the base distro and running it on mach-virt.
> 
> Does this work with ELF FDPIC or do you need binfmt-flat?
I use binfmt-flat, but that's because Marc (on Cc: now) created the base
BSP for me that way. I don't know what ELF FDPIC is.

> > > Do you prevent building such a kernel in Kconfig?
> > I'm sure my Kconfig magic isn't waterproof. It took me a few tries to
> > expand the multiarch architecture selection to make v7-m selectable at
> > all.
> 
> Ok, I can have a look and give you suggestions for how it needs to be
> phrased if it currently allows broken (non-building) combinations.
You have the chance now to comment in the respective thread.

Best regards
Uwe

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

  reply	other threads:[~2013-09-30 15:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 19:58 [PATCH v2] ARM: new platform for Energy Micro's EFM32 Cortex-M3 SoCs Uwe Kleine-König
2013-09-17 20:45 ` Arnd Bergmann
2013-09-18 15:34   ` Uwe Kleine-König
2013-09-19 11:28     ` Arnd Bergmann
2013-09-19 11:34       ` Sebastian Hesselbarth
2013-09-19 12:19         ` Uwe Kleine-König
2013-09-26  9:42   ` Uwe Kleine-König
2013-09-27 21:44     ` Arnd Bergmann
2013-09-27 21:55       ` Russell King - ARM Linux
2013-09-28 19:15       ` Uwe Kleine-König
2013-09-29 19:00         ` Arnd Bergmann
2013-09-30 15:49           ` Uwe Kleine-König [this message]
2013-10-01 10:38         ` Jonathan Austin
2013-09-24 14:00 ` [PATCH] ARM: DEBUG_LL on efm32 SoCs Uwe Kleine-König

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=20130930154912.GE2548@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).