From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14221] New: mv-ddr-marvell fails license validation
Date: Wed, 22 Sep 2021 15:22:14 +0000 [thread overview]
Message-ID: <bug-14221-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14221
Bug ID: 14221
Summary: mv-ddr-marvell fails license validation
Product: buildroot
Version: 2021.02.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: nyanyamiau@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
With mv-ddr-marvell selected:
make legal-info
This fails with the following message:
>>> mv-ddr-marvell 305d923e6bc4236cd3b902f6679b0aef9e5fa52d Collecting legal info
ERROR: ddr3_init.c has wrong sha256 hash:
ERROR: expected:
69208236fc322026920b92d1d839ebdc521ca65379bfdb3368a24945e794fc78
ERROR: got :
48bb930b6fbc3f5db72e29c849b096df3868e4a6d2bdc0e2dd3365c768241cd5
ERROR: Incomplete download, or man-in-the-middle (MITM) attack
make[1]: *** [boot/mv-ddr-marvell/mv-ddr-marvell.mk:15:
mv-ddr-marvell-legal-info] Error 1
Blame: 2cfdf8b8a269a2c3205f706315469051aa450d6b
ddr3_init.c hash has not been updated
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-09-22 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 15:22 bugzilla [this message]
2021-09-23 15:39 ` [Buildroot] [Bug 14221] mv-ddr-marvell fails license validation bugzilla
2021-09-24 19:47 ` 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-14221-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