Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] configs/marvell_ca9_armv7_le_hfp_defconfig
Date: Wed, 05 Aug 2015 16:36:34 -0300	[thread overview]
Message-ID: <55C265C2.6060608@zacarias.com.ar> (raw)
In-Reply-To: <944894A3EB1D044A9003B2F944389BB20474AD9109@svr-wa-exch1.atg.lc>

On 05/08/15 14:04, Lee, Tommy wrote:

> _Question_
>
> The docs/manual/manual.pdf Section 3.1 (Configuration and general usage)
> lists a toolchain sub-folder in the output folder. My output folder does
> not have the such sub-folder. You probably know the reason for this missing.

Hi.
Can you point to the exact location in the manual (say, page in the 
online pdf) where this is so?
Or if it's in the old (Marvell) buildroot then it likely doesn't apply 
to current releases - new features, cleaning up and other factors can 
change that, manuals are normally attached to explicit buildroot releases.

> _Issue_
>
> The Buildroot-2015.05/configs does not have the
> marvell_ca9_armv7_le_uclibc_sfp_reduced_defconfig file in it. I wonder
> if the file needs to be added into the Buildroot-2015.08 release.

That still sounds like a Marvell config from their BR, with the 
difference between both being the floating-point strategy (i assume 
sfp=soft, hfp=hard), which are easy configuration options in mainstream 
buildroot.
Regards.

  reply	other threads:[~2015-08-05 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 17:04 [Buildroot] configs/marvell_ca9_armv7_le_hfp_defconfig Lee, Tommy
2015-08-05 19:36 ` Gustavo Zacarias [this message]
     [not found]   ` <944894A3EB1D044A9003B2F944389BB20474AD913B@svr-wa-exch1.atg.lc>
2015-08-06 13:12     ` Gustavo Zacarias
  -- strict thread matches above, loose matches on Subject: below --
2015-07-31  0:08 Lee, Tommy
2015-07-31  6:04 ` Thomas Petazzoni

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=55C265C2.6060608@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox