summaryrefslogtreecommitdiffstats
path: root/meta-agl-bsp/meta-ti/recipes-kernel/linux/files/dcan2_pinmux_enable.patch
diff options
context:
space:
mode:
authorPaul Barker <paul.barker@sancloud.co.uk>2019-06-06 09:22:45 +0000
committerPaul Barker <paul.barker@sancloud.co.uk>2019-06-06 09:34:42 +0000
commit351235222c0228e58e3a14e18766eea52cdfe47e (patch)
tree53c4617154b8188094bb053e8ed33fa5f5fa8cda /meta-agl-bsp/meta-ti/recipes-kernel/linux/files/dcan2_pinmux_enable.patch
parenta039cce0977ca33e4532de87fd4a1867cc7b21a7 (diff)
Pin SRCREV used by ti-sgx-ddk-km
The commit of the omap5-sgx-ddk-linux git repository used by the ti-sgx-ddk-km recipe is changed by recent commits to meta-ti to introduce generic support for armel (soft-float) targets. This conflicts with the existing patch in meta-agl which adds support for our toolchain. The simplest fix is to pin to a working commit by setting SRCREV to the previous commit on the same branch. This is the same commit that is currently used and so it won't have any effect until the meta-ti layer itself is updated. For reference, the commit in question can be seen here: https://git.ti.com/graphics/omap5-sgx-ddk-linux/commit/dbdbd9309a58ee723fc827ef5fd45c28347cf61f Bug-AGL: SPEC-2490 Change-Id: I2924cdadd697680567a9378eb3242f8dd526a429 Signed-off-by: Paul Barker <paul.barker@sancloud.co.uk>
Diffstat (limited to 'meta-agl-bsp/meta-ti/recipes-kernel/linux/files/dcan2_pinmux_enable.patch')
0 files changed, 0 insertions, 0 deletions