search

Pelagicore / meta-pelux

PELUX is an open source, GENIVI compliant development platform that supports the Qt Automotive Suite
https://pelux.io
MIT License
39 stars 28 forks source link

variant/local.conf.sample: Include bz2 type #330

Closed fhajredini closed 5 years ago

fhajredini commented 5 years ago

Signed-off-by: Fisnik Hajredini fhajredini@luxoft.com

sashko commented 5 years ago

what for?

fhajredini commented 5 years ago

what for?

Updated the commit message

sashko commented 5 years ago 
it will be a compressed image (~1GB) and it will be faster to download
it supports compressed images for faster flashing to disk.

wait, what? so will we get, two images: wic and wic.bz2? how can one flash bz2 one without decompressing it?

martin-ejdestig commented 5 years ago

how can one flash bz2 one without decompressing it?

bmaptool takes care of decompressing it: https://github.com/intel/bmap-tools/blob/master/docs/README#L236

(Presumably, I have not tried it myself yet. :)

sashko commented 5 years ago

how can one flash bz2 one without decompressing it?

bmaptool takes care of decompressing it: https://github.com/intel/bmap-tools/blob/master/docs/README#L236

(Presumably, I have not tried it myself yet. :)

okay, great. @fhajredini can you confirm? also, double check whether we need wic.bmap after this change or wic.bmap.bz2 would be enough. don't forget about updating docs as well.

fhajredini commented 5 years ago

how can one flash bz2 one without decompressing it?

bmaptool takes care of decompressing it: https://github.com/intel/bmap-tools/blob/master/docs/README#L236 (Presumably, I have not tried it myself yet. :)

okay, great. @fhajredini can you confirm? also, double check whether we need wic.bmap after this change or wic.bmap.bz2 would be enough. don't forget about updating docs as well.

We still need wic.bmap

sashko commented 5 years ago

local.conf.sample: add wic.bmap.bz2 to IMAGE_FSTYPES / generate wic.bmap.bz2 IMAGE_FSTYPE for Intel and ARP

fhajredini commented 5 years ago

Just checked again, it can be flashed without bmap file too, but that wouldnt be so smart as it increases the time of the flashing a lot. I think that its the bmap file which takes use of the sparse bytes..

sashko commented 5 years ago

Just checked again, it can be flashed without bmap file too, but that wouldnt be so smart as it increases the time of the flashing a lot. I think that its the bmap file which takes use of the sparse bytes..

I am not sure I understood you: isn't wic.bmap.bz just a compressed version of wic.bmap?

fhajredini commented 5 years ago

Just checked again, it can be flashed without bmap file too, but that wouldnt be so smart as it increases the time of the flashing a lot. I think that its the bmap file which takes use of the sparse bytes..

I am not sure I understood you: isn't wic.bmap.bz just a compressed version of wic.bmap?

No, wic.bmap is a file of 8KB. As far as i understand, its just a file which maps the image for easier flashing.. now the actual image is still required, and that can be a raw image(.wic) or a compressed image(.wic.bz2). Bmaptools can flash a compressed image on the fly. It can compress it with, or without the bmap file, but without it, it will take a longer time.

sashko commented 5 years ago

title is still ambiguous

fhajredini commented 5 years ago

bmap has already been included on the previous commits. This is just having a compressed image as an artifact.