From: manabian@gmail.com (Joachim Eastwood)
To: linux-arm-kernel@lists.infradead.org
Subject: Cortex-M and zImage
Date: Tue, 16 Sep 2014 22:25:02 +0200 [thread overview]
Message-ID: <CAGhQ9VzzSq4P5BKM3UBBCPT61g3T1RHFhttfA-KkWGCcrjaW6A@mail.gmail.com> (raw)
Hi,
I am working on Linux support for the NXP LPC18xx/43xx family of
Cortex-M3/M4 microcontrollers. Building zImage for Cortex-M fails
with the following two errors:
error: arch/arm/boot/compressed/piggy.gzip.o: Conflicting architecture
profiles M/A
linux/arch/arm/boot/compressed/head.S:794: undefined reference to
`CONFIG_PROCESSOR_ID'
The last error is easy to fix. But the first about conflicting arch is
harder.
As far as I know zImage on Cortex-M is not supported or not tested.
Are there any plans to support zImage on Cortex-M?
If so does anyone have an idea how the conflicting arch issue could
be solved?
btw, building with 'make Image' works fine and I have been running
Linux for a while on the NXP LPC4357.
regards
Joachim Eastwood
next reply other threads:[~2014-09-16 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 20:25 Joachim Eastwood [this message]
2014-09-17 6:11 ` Cortex-M and zImage Uwe Kleine-König
2014-09-17 6:55 ` Joachim Eastwood
2014-09-17 7:05 ` Uwe Kleine-König
2014-09-17 21:06 ` Joachim Eastwood
2014-09-17 8:47 ` Russell King - ARM Linux
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=CAGhQ9VzzSq4P5BKM3UBBCPT61g3T1RHFhttfA-KkWGCcrjaW6A@mail.gmail.com \
--to=manabian@gmail.com \
--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).