26 replies to this topic

[hemertje]

At the dreamboxes the bootlogo has to share the partition with the kernel, so it cannot be too big else the logo wont fit as you see with the current new logo...

Due to this the bottom is cut off

We are working on a new small size logo that fit, but the side effect is that the logo will get artifacts, sadly but nothing that we can do about due to DMM's drivers

[escalibur]

So it's still not safe to update to the latest version?

[hemertje]

i was only referring to the bootlogo

[Bernado]

At the dreamboxes the bootlogo has to share the partition with the kernel, so it cannot be too big else the logo wont fit as you see with the current new logo...

Due to this the bottom is cut off

We are working on a new small size logo that fit, but the side effect is that the logo will get artifacts, sadly but nothing that we can do about due to DMM's drivers

Thanks for explanation, now i know why i was not effected - using bootlogo #1 in my builds on dreamboxes from this thread (53 kB instead of 140 kB of currently used abstraced logo):

http://openpli.org/f...e__hl__bootlogo

[hemertje]

Hi Bernado,

can you find out for us what maximum size of the mvi file might be without getting the black bottom on a DMM box...

thx!

[Bernado]

Hi hemertje,

did some quick testing on dm800se with varios mvis - 195.095 bytes is still a bit too big, but only small black bottom line left (~ 20 pixel)

i suppose something between 170-190 kB is maximum available size (with current drivers/kernel)

biggest one working without cutting off was 168.960 bytes

Edited by Bernado, 28 December 2012 - 18:14.

[Bernado]

just noticed commit from today, no cutting off with 188.099 bytes, thanks

http://openpli.git.s...c6fa72f73b82cb2