All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] add support iMX8MQ-evk board
Date: Tue, 27 Feb 2018 09:36:42 +0100	[thread overview]
Message-ID: <06002b0f-b4ec-f35b-79c6-2c9cfb016516@mind.be> (raw)
In-Reply-To: <CAPP7BN0vqy-J=6GE+S5cEqwwEhC-yiJLjvrZttqEC7c2XFLMJQ@mail.gmail.com>



On 27-02-18 05:15, Erik Larsson wrote:
> Hi Gary,
> 
> 2018-02-23 11:43 GMT+01:00 Gary Bisson <gary.bisson@boundarydevices.com>:
>> Hi Erik,
>>
>> On Thu, Feb 22, 2018 at 11:02:58AM +0100, Erik Larsson wrote:
>>> Signed-off-by: Erik Larsson <karl.erik.larsson@gmail.com>
>>> ---
>>>  .../common/imx/genimage.cfg.template_imx8          |  40 ++
>>>  board/freescale/common/imx/post-image.sh           |  10 +-
>>>  board/freescale/imx8mqevk/linux-4.9.config         | 625 +++++++++++++++++++++
>>>  configs/freescale_imx8mqevk_defconfig              |  37 ++
>>
>> Why do we copy the defconfig in board folder although it present in the
>> kernel tree directly?
> The reason I add the kernel defconfig into the board folder is that
> NXP removed all defconfigs and renamed the valid one to 'defconfig' in
> the kernel. This makes it impossible (at least I think so) to use an
> in tree defconfig.
> 
> $ ls -l arch/arm64/configs/
> total 16
> -rw-r--r-- 1 erik erik 14337 dec 15 02:52 defconfig
> 
> Copying it into the board folder was the best solution available.

 You should be able to use that in-tree defconfig with
BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2018-02-27  8:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 10:02 [Buildroot] [PATCH v2 0/3] Initial support for NXP iMX8 (imx8mq-evk) Erik Larsson
2018-02-22 10:02 ` [Buildroot] [PATCH v2 1/3] imx-mkimage: new package Erik Larsson
2018-02-22 14:37   ` Marcus Folkesson
2018-02-25  8:43   ` Baruch Siach
2018-02-27  4:26     ` Erik Larsson
2018-02-22 10:02 ` [Buildroot] [PATCH v2 2/3] firmware-imx: add support for iMX8M firmware Erik Larsson
2018-02-23 10:40   ` Gary Bisson
2018-02-22 10:02 ` [Buildroot] [PATCH v2 3/3] add support iMX8MQ-evk board Erik Larsson
2018-02-23 10:43   ` Gary Bisson
2018-02-27  4:15     ` Erik Larsson
2018-02-27  8:36       ` Arnout Vandecappelle [this message]
2018-02-25  7:43   ` Baruch Siach
2018-02-25 21:20   ` Thomas Petazzoni
2018-02-22 14:30 ` [Buildroot] [PATCH v2 0/3] Initial support for NXP iMX8 (imx8mq-evk) Marcus Folkesson
2018-02-25 21:19 ` Thomas Petazzoni
2018-02-26  5:32   ` Erik Larsson

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=06002b0f-b4ec-f35b-79c6-2c9cfb016516@mind.be \
    --to=arnout@mind.be \
    --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.