From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jesse Taube <mr.bossman075@gmail.com>
Cc: festevam@gmail.com,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
maeva.manuel@oss.nxp.com, stephane.viau@oss.nxp.com,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v6] configs/imxrt1050-evk: New defconfig
Date: Wed, 9 Aug 2023 23:25:35 +0200 [thread overview]
Message-ID: <20230809232535.5da9862f@windsurf> (raw)
In-Reply-To: <20230102181603.3337480-1-Mr.Bossman075@gmail.com>
Hello Jesse,
On Mon, 2 Jan 2023 13:16:03 -0500
Jesse Taube <mr.bossman075@gmail.com> wrote:
> Add defconfig for imxrt1050-evk is a development board from NXP.
>
> Giulio and I worked on Linux and U-boot for this board. And now I'm
> adding support for the new board in Buildroot.
>
> The i.MXRTxxxx family spreads from i.MXRT1020 to i.MXRT1170 with the
> first one supporting 1 USB OTG & 100M ethernet with a cortex-M7@500Mhz
> up to the latter with i.MXRT1170 with cortex-M7@1Ghz and
> cortex-M4@400Mhz, 2MB of internal SRAM, 2D GPU, 2x 1Gb and
> 1x 100Mb ENET. The i.MXRT family is NXP's answer to STM32F7xx, as it
> uses only simple SDRAM, it gives the chance of a 4 or less layer PCBs.
> Seeing that these chips are comparable to the STM32F7xxs which have
> buildroot ported to them it seems reasonable to add support for them.
>
> https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-rt1050-evaluation-kit:MIMXRT1050-EVK
>
> Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com>
> Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>
> Reviewed-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> Tested-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Sorry for the super super long delay, but I have now applied this patch
to our next branch.
> diff --git a/DEVELOPERS b/DEVELOPERS
> index 59121c6a54..ee33c65fd4 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -1132,9 +1132,11 @@ F: package/webp/
> F: package/xapian/
>
> N: Giulio Benetti <giulio.benetti@benettiengineering.com>
> +F: board/freescale/imxrt1050evk/*
The * here is not needed. A directory is properly interpreted.
> +N: Jesse Taube <Mr.Bossman075@gmail.com>
> +F: board/freescale/imxrt1050evk/*
Same.
> +# Required tools to create the SD card image
> +BR2_PACKAGE_HOST_GENIMAGE=y
> +BR2_PACKAGE_HOST_MKPASSWD=y
I don't think mkpasswd is needed in your configuration, so I dropped
that.
Committed with those changes.
Possible improvements now:
- Update to newer kernel/U-Boot
- Use zImage instead of uImage for the kernel if possible
- Maybe use extlinux.conf in U-Boot if it's also possible
Nothing urgent, just suggestions.
Thanks for your contribution!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-09 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 18:16 [Buildroot] [PATCH v6] configs/imxrt1050-evk: New defconfig Jesse Taube
2023-01-02 20:23 ` Giulio Benetti
2023-08-09 21:25 ` Thomas Petazzoni via buildroot [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=20230809232535.5da9862f@windsurf \
--to=buildroot@buildroot.org \
--cc=festevam@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=maeva.manuel@oss.nxp.com \
--cc=mr.bossman075@gmail.com \
--cc=stephane.viau@oss.nxp.com \
--cc=thomas.petazzoni@bootlin.com \
/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.