From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14406] New: Support LPDDR4 variant i.MX8MN EVK board
Date: Wed, 01 Dec 2021 11:00:59 +0000 [thread overview]
Message-ID: <bug-14406-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14406
Bug ID: 14406
Summary: Support LPDDR4 variant i.MX8MN EVK board
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: zeno.endemann@kdab.com
CC: buildroot@uclibc.org
Target Milestone: ---
The existing freescale_imx8mnevk_defconfig builds an image for the DDR4 variant
of the dev board. This seems weird, as the LPDDR4 variant appears to be the
more common one (this is what I got when ordering the dev board from
www.nxp.com), and in the yocto layer the "default" config refers to the LPDDR4
variant as well (and one has to explicitly specify the DDR4 variant).
At the very least it would be nice if the board/freescale/imx8mnevk/readme.txt
could document what needs to be changed for the LPDDR4 variant. Even better
would be another defconfig. To be more in line with yocto it possibly might be
good to make the freescale_imx8mnevk_defconfig build the LPDDR4 variant, and
have a freescale_imx8mnevk_ddr4_defconfig.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-12-01 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 11:00 bugzilla [this message]
2024-06-15 15:00 ` [Buildroot] [Bug 14406] Support LPDDR4 variant i.MX8MN EVK board bugzilla
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=bug-14406-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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