Skip to contentSkip to conversation

Sharing TF-A with multiple BSP

DISCUSSION Joshua Watt 3 participants 5 messages May 11, 2020 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Continuing the outcome from a discussion that was on the OE-core mailing list, I've started converting some of the BSP layers I work on to use the trusted-firmware-a recipe from meta-arm as the canonical source of ATF instead of each of the implementing their own recipe. So far this has gone well except for one annoyance I've found: meta-arm has a layer dependency on meta-python, specifically for the optee recipe. Normally, this wouldn't be such a big deal, but in a ideal world there will now be a lot of BSP layers that depend on meta-arm to provide ATF, and it seems annoying to have to make all of those layers (transitively) depend on meta-python.

I can think of a few possible options:

1) Do nothing because no one other than me thinks this is a problem :)

2) Use BBFILES_DYNAMIC to make optee optional based on the presence of meta-python

3) Use PACKAGECONFIG to remove the python parts of optee (if that's even possible). They can be automatically added back if meta-python is present via BBFILES_DYNAMIC.

4) Remove the hard requirement of meta-python from meta-arm; it's only needed to build optee so the users can figure it out?

Anyone else have any ideas or thoughts?

Thanks,
Joshua Watt

#1 lore raw
Quoted 10 lines · Joshua Watt

Continuing the outcome from a discussion that was on the OE-core mailing list, I've started converting some of the BSP layers I work on to use the trusted-firmware-a recipe from meta-arm as the canonical source of ATF instead of each of the implementing their own recipe. So far this has gone well except for one annoyance I've
found: meta-arm has a layer dependency on meta-python, specifically for the optee recipe. Normally, this wouldn't be such a big deal, but in a ideal world there will now be a lot of BSP layers that depend on meta-arm to provide ATF, and it seems annoying to have to make all of those layers (transitively) depend on meta-python.

Yeah, I raised this issue over a month ago - unfortunately, nobody replied or acknowledged...

Quoted 3 lines

I can think of a few possible options:

1) Do nothing because no one other than me thinks this is a problem :)

Don't flatter yourself... :) :D J/k

Quoted 6 lines

2) Use BBFILES_DYNAMIC to make optee optional based on the presence of meta-python

3) Use PACKAGECONFIG to remove the python parts of optee (if that's even possible). They can be automatically added back if meta-python is present via BBFILES_DYNAMIC.

I don't think those are optional - they are used during the build to sign some parts. And also for ELF manipulations.

Quoted 5 lines

4) Remove the hard requirement of meta-python from meta-arm; it's only needed to build optee so the users can figure it out?

Anyone else have any ideas or thoughts?

I can think of couple more options:

5) there are only 3 python modules needed - pycrypto, pycryptodomex (actually a replacement for pycrypto, so upstream can drop first one) and pyelftools. Could probably try to make a case of moving them to OE-Core?

6) Like optee was inside own sub-layer meta-optee within meta-linaro, can look into separating it into meta-optee within meta-arm.

Quoted 5 lines

Thanks,
Joshua Watt

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

+ Khem

[apparently, nobody follows the list, so need to round up everyone interested] :)

Please see below for possible discussed options. IMHO, #5 would be ideal.

Quoted 58 lines · Denys Dmytriyenko
Quoted 10 lines · Joshua Watt

Continuing the outcome from a discussion that was on the OE-core mailing list, I've started converting some of the BSP layers I work on to use the trusted-firmware-a recipe from meta-arm as the canonical source of ATF instead of each of the implementing their own recipe. So far this has gone well except for one annoyance I've
found: meta-arm has a layer dependency on meta-python, specifically for the optee recipe. Normally, this wouldn't be such a big deal, but in a ideal world there will now be a lot of BSP layers that depend on meta-arm to provide ATF, and it seems annoying to have to make all of those layers (transitively) depend on meta-python.

Yeah, I raised this issue over a month ago - unfortunately, nobody replied or acknowledged...

Quoted 3 lines

I can think of a few possible options:

1) Do nothing because no one other than me thinks this is a problem :)

Don't flatter yourself... :) :D J/k

Quoted 6 lines

2) Use BBFILES_DYNAMIC to make optee optional based on the presence of meta-python

3) Use PACKAGECONFIG to remove the python parts of optee (if that's even possible). They can be automatically added back if meta-python is present via BBFILES_DYNAMIC.

I don't think those are optional - they are used during the build to sign some parts. And also for ELF manipulations.

Quoted 5 lines

4) Remove the hard requirement of meta-python from meta-arm; it's only needed to build optee so the users can figure it out?

Anyone else have any ideas or thoughts?

I can think of couple more options:

5) there are only 3 python modules needed - pycrypto, pycryptodomex (actually a replacement for pycrypto, so upstream can drop first one) and pyelftools. Could probably try to make a case of moving them to OE-Core?

6) Like optee was inside own sub-layer meta-optee within meta-linaro, can look into separating it into meta-optee within meta-arm.

Quoted 5 lines

Thanks,
Joshua Watt

#4 lore raw
Quoted 5 lines · Denys Dmytriyenko

+ Khem

[apparently, nobody follows the list, so need to round up everyone interested] :)

Admittedly I don't follow and this layer shows up because I need meta-ti just for beaglebone
which does not use optee, so not that interesting but I am on receiving end of this. I agree
option 5 is best and if, we could also move the recipe to meta-oe at least that can be a lesser
common place if not core.

Quoted 63 lines

Please see below for possible discussed options. IMHO, #5 would be ideal.

Quoted 58 lines · Denys Dmytriyenko
Quoted 10 lines · Joshua Watt

Continuing the outcome from a discussion that was on the OE-core mailing list, I've started converting some of the BSP layers I work on to use the trusted-firmware-a recipe from meta-arm as the canonical source of ATF instead of each of the implementing their own recipe. So far this has gone well except for one annoyance I've
found: meta-arm has a layer dependency on meta-python, specifically for the optee recipe. Normally, this wouldn't be such a big deal, but in a ideal world there will now be a lot of BSP layers that depend on meta-arm to provide ATF, and it seems annoying to have to make all of those layers (transitively) depend on meta-python.

Yeah, I raised this issue over a month ago - unfortunately, nobody replied or acknowledged...

Quoted 3 lines

I can think of a few possible options:

1) Do nothing because no one other than me thinks this is a problem :)

Don't flatter yourself... :) :D J/k

Quoted 6 lines

2) Use BBFILES_DYNAMIC to make optee optional based on the presence of meta-python

3) Use PACKAGECONFIG to remove the python parts of optee (if that's even possible). They can be automatically added back if meta-python is present via BBFILES_DYNAMIC.

I don't think those are optional - they are used during the build to sign some parts. And also for ELF manipulations.

Quoted 5 lines

4) Remove the hard requirement of meta-python from meta-arm; it's only needed to build optee so the users can figure it out?

Anyone else have any ideas or thoughts?

I can think of couple more options:

5) there are only 3 python modules needed - pycrypto, pycryptodomex (actually a replacement for pycrypto, so upstream can drop first one) and pyelftools. Could probably try to make a case of moving them to OE-Core?

6) Like optee was inside own sub-layer meta-optee within meta-linaro, can look into separating it into meta-optee within meta-arm.

Quoted 5 lines

Thanks,
Joshua Watt

#5 lore raw

Looping in OE-core. Specifically, would there be any push back to adding pycryptodomex and pyelftools to oe-core?

Quoted 67 lines · Khem Raj
Quoted 4 lines · Denys Dmytriyenko

+ Khem

[apparently, nobody follows the list, so need to round up everyone interested] :)

Admittedly I don't follow and this layer shows up because I need meta-ti just for beaglebone
which does not use optee, so not that interesting but I am on receiving end of this. I agree
option 5 is best and if, we could also move the recipe to meta-oe at least that can be a lesser
common place if not core.

Quoted 54 lines

Please see below for possible discussed options. IMHO, #5 would be ideal.

Quoted 50 lines · Denys Dmytriyenko
Quoted 10 lines · Joshua Watt

Continuing the outcome from a discussion that was on the OE-core mailing list, I've started converting some of the BSP layers I work on to use the trusted-firmware-a recipe from meta-arm as the canonical source of ATF instead of each of the implementing their own recipe. So far this has gone well except for one annoyance I've
found: meta-arm has a layer dependency on meta-python, specifically for the optee recipe. Normally, this wouldn't be such a big deal, but in a ideal world there will now be a lot of BSP layers that depend on meta-arm to provide ATF, and it seems annoying to have to make all of those layers (transitively) depend on meta-python.

Yeah, I raised this issue over a month ago - unfortunately, nobody replied or acknowledged...

Quoted 3 lines

I can think of a few possible options:

1) Do nothing because no one other than me thinks this is a problem :)

Don't flatter yourself... :) :D J/k

Quoted 6 lines

2) Use BBFILES_DYNAMIC to make optee optional based on the presence of meta-python

3) Use PACKAGECONFIG to remove the python parts of optee (if that's even possible). They can be automatically added back if meta-python is present via BBFILES_DYNAMIC.

I don't think those are optional - they are used during the build to sign some parts. And also for ELF manipulations.

Quoted 5 lines

4) Remove the hard requirement of meta-python from meta-arm; it's only needed to build optee so the users can figure it out?

Anyone else have any ideas or thoughts?

I can think of couple more options:

5) there are only 3 python modules needed - pycrypto, pycryptodomex (actually a replacement for pycrypto, so upstream can drop first one) and pyelftools. Could probably try to make a case of moving them to OE-Core?

6) Like optee was inside own sub-layer meta-optee within meta-linaro, can look into separating it into meta-optee within meta-arm.

Quoted 3 lines

Thanks,
Joshua Watt