Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
M
meta-elphel393
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
Elphel
meta-elphel393
Commits
475583f7
Commit
475583f7
authored
Sep 06, 2019
by
Oleg Dzhimiev
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
bumped recipe version to 2019.1 but kept kernel at 4.14 (vs 4.19)
parent
01822977
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
0 deletions
+8
-0
linux-xlnx_2019.1.bbappend
recipes-kernel/linux/linux-xlnx_2019.1.bbappend
+8
-0
No files found.
recipes-kernel/linux/linux-xlnx_201
8.3
.bbappend
→
recipes-kernel/linux/linux-xlnx_201
9.1
.bbappend
View file @
475583f7
...
@@ -19,9 +19,17 @@ linux-elphel_label= "https://${ELPHELGITHOST}/Elphel/linux-elphel.git"
...
@@ -19,9 +19,17 @@ linux-elphel_label= "https://${ELPHELGITHOST}/Elphel/linux-elphel.git"
linux-elphel_branch= "master"
linux-elphel_branch= "master"
linux-elphel_gitdir= "${WORKDIR}/linux-elphel"
linux-elphel_gitdir= "${WORKDIR}/linux-elphel"
LINUX_VERSION = "4.14"
XILINX_RELEASE_VERSION = "v2018.3"
KBRANCH = "xlnx_rebase_v4.14"
LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
# linux xilinx hash
# linux xilinx hash
#SRCREV = "9c2e29b2c81dbb1efb7ee4944b18e12226b97513"
#SRCREV = "9c2e29b2c81dbb1efb7ee4944b18e12226b97513"
# for 4.14:
SRCREV = "eeab73d1207d6fc2082776c954eb19fd7290bfbe"
SRCREV = "eeab73d1207d6fc2082776c954eb19fd7290bfbe"
# for 4.19
#SRCREV = "9811303824b66a8db9a8ec61b570879336a9fde5"
# To use the latest leave: "" - (=empty)
# To use the latest leave: "" - (=empty)
linux-elphel_srcrev= ""
linux-elphel_srcrev= ""
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment