Skip to contentSkip to conversation

recipes-graphics: Enable SGX drivers for Beagleboard and Pandaboard

RFC In review Andrew F. Davis 2 participants 3 messages Jan 31, 2020

lore
Share & tools
lore
#0 lore raw

RFC 1/1 recipes-graphics: Enable SGX drivers for Beagleboard and Pandaboard

These boards have SGX GPUs but do not build as this recipe is not compatible with them, add compatibles for these machines.

---

Currently and RFC until I can get these binaries pushed to the git.ti.com/graphics/omap5-sgx-ddk repos.

Tested working locally on latest with a Beagleboard and a Pandaboard.

 recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb | 4 +++-
 recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +3 -1
index 751dfc74..05bca918 100644
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = "file://eurasia_km/README;beginline=13;endline=22;md5=74506d9
 
 inherit module
 
-COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k3"
+COMPATIBLE_MACHINE = "pandaboard|beagleboard|ti33x|ti43x|omap-a15|k3"
 
 MACHINE_KERNEL_PR_append = "s"
 PR = "${MACHINE_KERNEL_PR}"
@@ -30,6 +30,8 @@ TARGET_PRODUCT_omap-a15 = "jacinto6evm"
 TARGET_PRODUCT_ti33x = "ti335x"
 TARGET_PRODUCT_ti43x = "ti437x"
 TARGET_PRODUCT_k3 = "ti654x"
+TARGET_PRODUCT_beagleboard = "ti343x"
+TARGET_PRODUCT_pandaboard = "ti443x"
 
 EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" TARGET_PRODUCT=${TARGET_PRODUCT} WINDOW_SYSTEM=nulldrmws'
 
recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb +3 -1
index ecf3ffcc..e3b9b4d1 100644
@@ -4,7 +4,7 @@ LICENSE = "TI-TSPA"
 LIC_FILES_CHKSUM = "file://TI-Linux-Graphics-DDK-UM-Manifest.doc;md5=b17390502bc89535c86cfbbae961a2a8"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
-COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k3"
+COMPATIBLE_MACHINE = "pandaboard|beagleboard|ti33x|ti43x|omap-a15|k3"
 
 PR = "r34"
 
@@ -17,6 +17,8 @@ TARGET_PRODUCT_omap-a15 = "jacinto6evm"
 TARGET_PRODUCT_ti33x = "ti335x"
 TARGET_PRODUCT_ti43x = "ti437x"
 TARGET_PRODUCT_k3 = "ti654x"
+TARGET_PRODUCT_beagleboard = "ti343x"
+TARGET_PRODUCT_pandaboard = "ti443x"
 
 INITSCRIPT_NAME = "rc.pvr"
 INITSCRIPT_PARAMS = "defaults 8"
Signature · 1 line
2.17.1
#1 lore raw
Quoted 10 lines · Andrew F. Davis

These boards have SGX GPUs but do not build as this recipe is not compatible with them, add compatibles for these machines.

---

Currently and RFC until I can get these binaries pushed to the git.ti.com/graphics/omap5-sgx-ddk repos.

Tested working locally on latest with a Beagleboard and a Pandaboard.

Super! Thanks for doing it!

Quoted 9 lines
 recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb | 4 +++-
 recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +0 -0
index 751dfc74..05bca918 100644

recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb LIC_FILES_CHKSUM = "file://eurasia_km/README;beginline=13;endline=22;md5=74506d9 · line 8

Quoted 5 lines
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +1 -1
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = "file://eurasia_km/README;beginline=13;endline=22;md5=74506d9
 
 inherit module
 
-COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k3"
+COMPATIBLE_MACHINE = "pandaboard|beagleboard|ti33x|ti43x|omap-a15|k3"

Can we use omap3 and omap4 SOC_FAMILY overrides instead of specific boards?

Quoted 36 lines
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +2 -0
 MACHINE_KERNEL_PR_append = "s"
 PR = "${MACHINE_KERNEL_PR}"
@@ -30,6 +30,8 @@ TARGET_PRODUCT_omap-a15 = "jacinto6evm"
 TARGET_PRODUCT_ti33x = "ti335x"
 TARGET_PRODUCT_ti43x = "ti437x"
 TARGET_PRODUCT_k3 = "ti654x"
+TARGET_PRODUCT_beagleboard = "ti343x"
+TARGET_PRODUCT_pandaboard = "ti443x"
 
 EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" TARGET_PRODUCT=${TARGET_PRODUCT} WINDOW_SYSTEM=nulldrmws'
 
recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb +3 -1
index ecf3ffcc..e3b9b4d1 100644
@@ -4,7 +4,7 @@ LICENSE = "TI-TSPA"
 LIC_FILES_CHKSUM = "file://TI-Linux-Graphics-DDK-UM-Manifest.doc;md5=b17390502bc89535c86cfbbae961a2a8"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
-COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k3"
+COMPATIBLE_MACHINE = "pandaboard|beagleboard|ti33x|ti43x|omap-a15|k3"
 
 PR = "r34"
 
@@ -17,6 +17,8 @@ TARGET_PRODUCT_omap-a15 = "jacinto6evm"
 TARGET_PRODUCT_ti33x = "ti335x"
 TARGET_PRODUCT_ti43x = "ti437x"
 TARGET_PRODUCT_k3 = "ti654x"
+TARGET_PRODUCT_beagleboard = "ti343x"
+TARGET_PRODUCT_pandaboard = "ti443x"
 
 INITSCRIPT_NAME = "rc.pvr"
 INITSCRIPT_PARAMS = "defaults 8"
Signature · 1 line
2.17.1
#2 lore raw
Quoted 25 lines · Denys Dmytriyenko
Quoted 10 lines · Andrew F. Davis

These boards have SGX GPUs but do not build as this recipe is not compatible with them, add compatibles for these machines.

---

Currently and RFC until I can get these binaries pushed to the git.ti.com/graphics/omap5-sgx-ddk repos.

Tested working locally on latest with a Beagleboard and a Pandaboard.

Super! Thanks for doing it!

Quoted 10 lines
 recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb | 4 +++-
 recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb | 4 +++-
 2 files changed, 6 insertions(+), 2 deletions(-)
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +0 -0
index 751dfc74..05bca918 100644
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = "file://eurasia_km/README;beginline=13;endline=22;md5=74506d9
 
Quoted 7 lines

recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb LIC_FILES_CHKSUM = "file://eurasia_km/README;beginline=13;endline=22;md5=74506d9 · line 8

Quoted 4 lines
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +1 -1
 inherit module
 
-COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k3"
+COMPATIBLE_MACHINE = "pandaboard|beagleboard|ti33x|ti43x|omap-a15|k3"

Can we use omap3 and omap4 SOC_FAMILY overrides instead of specific boards?

Problem is omap3 and omap4 have different SGX version depending on the exact chip, here is the current situation:

OMAP3430: sgx530-121
OMAP3530: sgx530-121
OMAP3630: sgx530-125
AM335x : sgx530-125
AM43xx : sgx530-125
OMAP4430: sgx540-120
OMAP4460: sgx540-120
OMAP4470: sgx544MP1-112
OMAP5432: sgx544MP2-105
AM57xx : sgx544MP2-116
AM654x : sgx544MP1-117

So for instance OMAP3530 has sgx530-121 but OMAP3630 has sgx530-125, so they will need different UM binaries even though both are OMAP3. For now it is easiest to partition based on the board as the board will give us the exact chip: beagleboard = OMAP3530 = sgx530-121 = ti343x. Kinda messy but the best I could come up with without changing the target product names all around.

Andrew

Quoted 37 lines
Quoted 37 lines
recipes-graphics/ti-img-sgx/ti-sgx-ddk-km_1.17.4948957.bb +2 -0
 MACHINE_KERNEL_PR_append = "s"
 PR = "${MACHINE_KERNEL_PR}"
@@ -30,6 +30,8 @@ TARGET_PRODUCT_omap-a15 = "jacinto6evm"
 TARGET_PRODUCT_ti33x = "ti335x"
 TARGET_PRODUCT_ti43x = "ti437x"
 TARGET_PRODUCT_k3 = "ti654x"
+TARGET_PRODUCT_beagleboard = "ti343x"
+TARGET_PRODUCT_pandaboard = "ti443x"
 
 EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" TARGET_PRODUCT=${TARGET_PRODUCT} WINDOW_SYSTEM=nulldrmws'
 
recipes-graphics/ti-img-sgx/ti-sgx-ddk-um_1.17.4948957.bb +3 -1
index ecf3ffcc..e3b9b4d1 100644
@@ -4,7 +4,7 @@ LICENSE = "TI-TSPA"
 LIC_FILES_CHKSUM = "file://TI-Linux-Graphics-DDK-UM-Manifest.doc;md5=b17390502bc89535c86cfbbae961a2a8"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
-COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k3"
+COMPATIBLE_MACHINE = "pandaboard|beagleboard|ti33x|ti43x|omap-a15|k3"
 
 PR = "r34"
 
@@ -17,6 +17,8 @@ TARGET_PRODUCT_omap-a15 = "jacinto6evm"
 TARGET_PRODUCT_ti33x = "ti335x"
 TARGET_PRODUCT_ti43x = "ti437x"
 TARGET_PRODUCT_k3 = "ti654x"
+TARGET_PRODUCT_beagleboard = "ti343x"
+TARGET_PRODUCT_pandaboard = "ti443x"
 
 INITSCRIPT_NAME = "rc.pvr"
 INITSCRIPT_PARAMS = "defaults 8"
Signature · 1 line
2.17.1