From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Stranz Jan-Marc <JM.Stranz@gantner-instruments.com>
Subject: Re: [ptxdist] Booting kernel crashes when using OSELAS.Toolchain-2014.12.1 for ARMv5TE
Date: Wed, 26 Aug 2015 09:23:18 +0200 [thread overview]
Message-ID: <201508260923.19016.jbe@pengutronix.de> (raw)
In-Reply-To: <86a99cfb77ba45c68f20cc8abf936019@GINS-EXC01.gins.local>
Hi Jan-Marc,
On Tuesday 25 August 2015 16:34:54 Stranz Jan-Marc wrote:
> thank you for the hints.
> Searching for an useful answer by Google isn't so easy, you'll get a lot of
> comments and I haven't the experience as a kernel developer has; I'm only
> a "user" of the components and tools.
So, it's time to become a kernel hacker! :)
> Now a I've got a hint to that the implementation of "memset"
> (/arch/arm/lib/memset.S) maybe the problem
> (https://bugs.linaro.org/show_bug.cgi?id=928#c7).
>
> I would try to compile the Linux kernel with an additional option
> "-fno-builtin-memset". How can I do that?
> PTXdist provides a rule "kernel.make".
> How should I modify this rule in order to activate the additional option
> "-fno-builtin-memset"?
I guess by applying the two memset patches Erwin mentioned, this question is
obsolete?
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-08-26 7:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 14:34 Stranz Jan-Marc
2015-08-26 7:23 ` Juergen Borleis [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-25 15:17 Stranz Jan-Marc
2015-08-26 7:23 ` Juergen Borleis
2015-08-26 7:27 ` Bruno Thomsen
2015-08-25 13:37 Stranz Jan-Marc
2015-08-25 14:01 ` Juergen Borleis
2015-08-25 14:40 ` Erwin Rol
2015-08-25 11:56 Stranz Jan-Marc
2015-08-25 12:23 ` Lucas Stach
2015-08-25 12:52 ` Juergen Borleis
2015-08-11 14:45 Stranz Jan-Marc
2015-08-24 9:19 ` Juergen Borleis
2015-08-11 14:16 Stranz Jan-Marc
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=201508260923.19016.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=JM.Stranz@gantner-instruments.com \
--cc=ptxdist@pengutronix.de \
/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