From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] configs/marvell_ca9_armv7_le_hfp_defconfig
Date: Thu, 06 Aug 2015 10:12:55 -0300 [thread overview]
Message-ID: <55C35D57.8000501@zacarias.com.ar> (raw)
In-Reply-To: <944894A3EB1D044A9003B2F944389BB20474AD913B@svr-wa-exch1.atg.lc>
On 05/08/15 17:47, Lee, Tommy wrote:
> Gustavo,
>
> Please view my replies.
>
> Tommy
Hi Tommy, try keeping the list on CC, someone else might be interested
or elaborate more.
> Can you point to the exact location in the manual (say, page in the
> online pdf) where this is so?
>
> Page 4/25.
>
> 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.
>
> The path to the manual.pdf is ?/
> buildroot-2015.05/docs/manual/manual.pdf. Last week I sued this PDF and
> succeeded in the make process with the external
> marvell_ca9_armv7_le_hfp_defconfig.
Hmm i'm still failing to find this in the online documentation at:
http://www.buildroot.net/downloads/manual/manual.pdf
Which as of this writing corresponds to the 2015.05 release.
In fact the pdf isn't shipped with releases and according to what you
wrote below you've got marvell files in the 2015.05 buildroot dir so
maybe it's still some old manual?
> With the above information there might be a strategy to include those
> defconfig files into the forthcoming BR release.
Normally defconfigs are submitted by contributors or companies if they
decide to make them clean/generic/minimal-enough for them to be
incorporated into buildroot releases.
In the end it's up to someone having hardware to test submitting them,
maybe you can do that?
Regards.
next prev parent reply other threads:[~2015-08-06 13:12 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
[not found] ` <944894A3EB1D044A9003B2F944389BB20474AD913B@svr-wa-exch1.atg.lc>
2015-08-06 13:12 ` Gustavo Zacarias [this message]
-- 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=55C35D57.8000501@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