View Single Post
Old 09-04-2015, 11:18 AM   #2
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
It makes sense. Although in case of my H2O it does not make any difference.

In my package there are two files:

u-boot_lpddr2_512-E606G0-LPDDR2.bin
u-boot_mddr_256-E606F0B-K4X2G323PC.bin

But it would look for u-boot_mddr_512-E606G0-LPDDR2.bin (which does not exist) so with and without the change it would end up using u-boot_lpddr2_512-E606G0-LPDDR2.bin instead.

Have you checked whether it actually affects your reader?

It should be reported to Kobo in any case, it looks unintentional. Although I guess if they actually installed the wrong bootloader for a device they would notice? (Presumably it would cause booting problems or similar?)
frostschutz is offline   Reply With Quote