Approved version. Approved on: 11:58, 7 October 2019
[unchecked revision] | [quality revision] |
Gerald Baeza (talk | contribs)
m
|
|
It is possible to accelerate JPEG compression and decompression by replacing the default libjpeg[1] library with the libjpeg-turbo[2]library that uses the Arm® NEON™ technology.
dpkg -l | grep jpeg ... Hardware accelerated JPEG compression/decompression library ...
Please refer to the OpenEmbedded libjpeg-turbo recipe documentation[3]
It is possible to accelerate JPEG compression and decompression by replacing the default libjpeg<ref>http://libjpeg.sourceforge.net/ libjpeg official web site</ref> library with the libjpeg-turbo<ref>https://libjpeg-turbo.org/ libjpeg-turbo official web site</ref>library that uses the [[NEON_overview | Arm<sup>®</sup> NEON<sup>™</sup>]] technology. == How to check the libjpeg-turbo installation == {{Board$}} dpkg -l | grep jpeg ... '''Hardware accelerated JPEG compression/decompression library''' ... == How to add the libjpeg-turbo in your distribution == Please refer to the OpenEmbedded libjpeg-turbo recipe documentation<ref>https://layers.openembedded.org/rrs/recipedetail/OE-Core/45003/ OpenEmbedded libjpeg-turbo recipe documentation</ref> == References ==<references/> <noinclude> {{PublicationRequestId | xxxxx | 2019-xx-xx | xxxxx}} [[Category:How to run use cases]][[Category:Arm processors]]</noinclude>
Line 16: | Line 16: | ||
{{PublicationRequestId | xxxxx | 2019-xx-xx | xxxxx}} |
{{PublicationRequestId | xxxxx | 2019-xx-xx | xxxxx}} |
||
[[Category:How to run use cases]] |
[[Category:How to run use cases]] |
||
− | |||
</noinclude> |
</noinclude> |