From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 43fa700e11020261935ab9c1cb395eb3d9f4f4b3
Date: Thu, 05 Dec 2019 17:55:41 +0000 [thread overview]
Message-ID: <47TNg212WLz2y3q@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2374 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 43fa700e11020261935ab9c1cb395eb3d9f4f4b3 (commit)
from 6fb7936c1650ea18b4690ec2f60be8b7640022a2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 43fa700e11020261935ab9c1cb395eb3d9f4f4b3
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Dec 5 18:53:16 2019 +0100
pcengines-firmware: update to 4.10.0.3
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/pcengines-apu-firmware | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
Difference in files:
diff --git a/lfs/pcengines-apu-firmware b/lfs/pcengines-apu-firmware
index 8b5c99412..71d8eea26 100644
--- a/lfs/pcengines-apu-firmware
+++ b/lfs/pcengines-apu-firmware
@@ -24,14 +24,14 @@
include Config
-VER = 4.10.0.0
+VER = 4.10.0.3
THISAPP = pcengines-apu-firmware-$(VER)
DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = pcengines-apu-firmware
-PAK_VER = 3
+PAK_VER = 4
SUP_ARCH = i586 x86_64
DEPS = "firmware-update"
@@ -53,11 +53,11 @@ apu3_v$(VER).rom = $(DL_FROM)/apu3_v$(VER).rom
apu4_v$(VER).rom = $(DL_FROM)/apu4_v$(VER).rom
apu5_v$(VER).rom = $(DL_FROM)/apu5_v$(VER).rom
-apu1_v$(VER).rom_MD5 = 21c754ae5390722e04aa7ea55e339478
-apu2_v$(VER).rom_MD5 = a509bc0384ba4f368bda267b8ed1761d
-apu3_v$(VER).rom_MD5 = 6951e3c8742dab67c84ef467c69edd66
-apu4_v$(VER).rom_MD5 = 0b30b739fccd22c43a13023c2bb7e867
-apu5_v$(VER).rom_MD5 = c1b5b9f393a099f0952b4138bc71901e
+apu1_v$(VER).rom_MD5 = f996d2272685683b1bf8be1f27b44f18
+apu2_v$(VER).rom_MD5 = 1ec2df4c0f9be2443192fead8e3b49e9
+apu3_v$(VER).rom_MD5 = 4a5cee9b621432627d7f3dcbb6191904
+apu4_v$(VER).rom_MD5 = a4a8bd06ebfa88907f5a4ddb6d7c3edc
+apu5_v$(VER).rom_MD5 = c389d490d02810bf65f0f3abb461070e
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-12-05 17:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47TNg212WLz2y3q@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.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