From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] board: Add support for Engicam i.CoreM6 Quad
Date: Fri, 24 Mar 2017 13:49:34 +0100 [thread overview]
Message-ID: <20170324134934.4b89a5bc@free-electrons.com> (raw)
In-Reply-To: <CAMty3ZA275KNiBcuM_YvZVmYcQQXp-Zq2R0o7_y2w7p6xxfZ-Q@mail.gmail.com>
Hello,
On Fri, 24 Mar 2017 16:08:22 +0530, Jagan Teki wrote:
> > Also, your defconfig should be named engicam_imx6q_icore_defconfig.
>
> Just for my understanding, why we add prefix engicam_ here because
> these boards always use Mainline code instead of freescale or some
> other source. I guess the reason behind
> freescale_imx6qsabresd_defconfig and imx6q-sabresd_defconfig based on
> the source where it cloned is that correct?
No, the main reason is just inconsistency I'd say. Ideally, all
defconfigs should follow this <vendor>_<product>_defconfig format I
believe.
> > Please use a fixed version of U-Boot.
>
> I'm planning to sync with Latest sources instead of some specific
> version, so-that I don't need to change my config again for next
> available/suitable version of source.
That's not how our defconfigs work. We want to build a fixed version of
the kernel and U-Boot, which has been tested by the person submitting
the defconfig. So please adopt the convention used in other defconfigs,
thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-24 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 11:01 [Buildroot] [PATCH 1/2] uboot: Config.in: Update BR2_TARGET_UBOOT_SPL_NAME help text Jagan Teki
2017-03-14 11:01 ` [Buildroot] [PATCH 2/2] board: Add support for Engicam i.CoreM6 Quad Jagan Teki
2017-03-19 14:20 ` Thomas Petazzoni
[not found] ` <CAMty3ZA275KNiBcuM_YvZVmYcQQXp-Zq2R0o7_y2w7p6xxfZ-Q@mail.gmail.com>
2017-03-24 12:49 ` Thomas Petazzoni [this message]
2017-03-14 22:39 ` [Buildroot] [PATCH 1/2] uboot: Config.in: Update BR2_TARGET_UBOOT_SPL_NAME help text 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=20170324134934.4b89a5bc@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox