On 14 Nov 2023, at 21:04, Dmitry Baryshkov via lists.openembedded.org <[email protected]> wrote: > > Android-targeted devices support so called sparse image format. This is > the raw filesystem image with dropped zero blocks. This way the image > takes less space and the bootloaders and/or filesystem manipulation > tools can flash it quicker (as they do not have to write useless > sequences of zeroes). > > Add new image conversion type called 'sparse'to be able to generate > filesystem images in the sparse format.
These files are not traditional sparse files but a new format which empty blocks identified in them, right? Then this name is very confusing and as RP says, maybe android-sparse is better. It’s a shame to have two identical tools, bmap-tools and this... > +CONVERSION_DEPENDS_sparse = "rust-android-sparse-native” As conversion commands can be in any class, you could add a new class to whatever layer has this recipe instead of adding directly to core. Ross
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#190808): https://lists.openembedded.org/g/openembedded-core/message/190808 Mute This Topic: https://lists.openembedded.org/mt/102592509/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
