All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ext-toolchain-wrapper issues
Date: Wed, 8 Aug 2012 21:07:42 +0200	[thread overview]
Message-ID: <20120808210742.42e5fca6@skate> (raw)
In-Reply-To: <CAE9DZUQp8QONoyfsieHt=vfdk4xreqqY=yekTTHk5yPopSFGeQ@mail.gmail.com>

Hello,

Le Wed, 8 Aug 2012 11:12:59 -0500,
Dallas Clement <dallas.a.clement@gmail.com> a ?crit :

> Just wanted to get back with you on this and let you know that I
> narrowed this down further.  There is no fault with the
> ext-toolchain-wrapper code.  It does the right thing.  The problem
> with my Linux kernel not booting was caused by the use of an incorrect
> gcc tune parameter.  This came from a buildroot config file I got from
> Marvell.  I simply changed it as follows, and everything is fine now.
> 
> #BR2_GCC_TARGET_TUNE="marvell-fv7"
> BR2_GCC_TARGET_TUNE="cortex-a9"

Ok, thanks for the investigation. I guess -mtune=marvell-fv7 argument
is specific to the Marvell gcc compiler, I haven't heard of it before.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-08-08 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 17:21 [Buildroot] ext-toolchain-wrapper issues Dallas Clement
2012-08-04  9:19 ` Thomas Petazzoni
2012-08-04 16:25   ` Dallas Clement
2012-08-04 16:58     ` Thomas Petazzoni
2012-08-08 16:12       ` Dallas Clement
2012-08-08 19:07         ` Thomas Petazzoni [this message]

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=20120808210742.42e5fca6@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.