Quote:
Originally Posted by fastrobot
I didn't mention the inconsistency to you, rather it was to another poster; but I'll answer you anyway.
I know that the updates, which are partial replacements
|
Why do you think they are partial replacements? They don't include what is on the recovery partition. That has much the same files excluding nickel and related files. It also has a set of the files in the upgrade package as at device release. The factory reset simply reboots, formats the root and user partition and installs it's copy of the firmware files in exactly the same way that the upgrade does. And there has been at least one person who replaces the firmware files on the recovery partition with those from an upgrade package and the factory reset worked perfectly to give them that version.
Quote:
|
-- are in fact identical; because I know I use the same one for both the AuraHD and the Glo. It's not a matter of disbelief in you personally, it's rather I'm baffled as to why my kernel driver works on one device perfectly but is causing the other device to lock up semi-randomly. If they were truly identical, that shouldn't happen... but it does. There may be other explanations for why it's locking up besides differences in the Glo and AuraHD -- But I just can't think of any that make sense off the top of my head.
|
I'm pretty sure the Glo and Aura HD use different kernels. They share the same update package, but there are two uImage files in the package. One has an PCB identifier for the Aura HD as part of the name. They are different sizes, so I assume there is a difference in the code.
Quote:
Hmm... I didn't know that -- and hadn't thought about that, for I only compiled my driver against the source code in KoboLabs/Kobo-Reader/hw/imx507-aurahd. The reason is that I downloaded the git repository a month ago -- and there wan't a directory in my clone of the github labeled KoboGlo. So -- since the updates are identical, I assumed the kernel had to be identical.
I just went back to browse git-hub to point out which directory I compiled from, and to point out that there was only AuraHD and not a Glo directory -- but to my shock, I now notice that a Kobo Glo directory was added 20 days ago called "glohd".
sigh.
https://github.com/kobolabs/Kobo-Reader/tree/master/hw
So -- there's an another example of an inconsistency ... which if that kernel proves to be the Glo's kernel (and maybe it's not); it was a belated posting to KoboLabs which caused me to waste my time .... (and yours in dealing with me...).  It would have been nice if I knew for sure which kernel my Glo ran the first time I downloaded the repository.
|
Huh? The Glo code has been there for ages. The new one is for the Glo HD. The problem is that the labelling has changed. If you look inside "imx507", the uboot file is described as "kernel and bootloader for Kobo Glo, Mini, and newer Touch". That suggests to me that this is the code used for those three devices. They were released at the same time and probably share more hardware than the other devices. The newer devices have their own package. I think the "imx508" is for the first two versions of the Touch, and the others are for the three versions of the WiFi and the original Kobo.
Looking at these, it does make me question my statement about shared code trees. Hopefully they are snapshots taken for each of the devices from the shared code. Someone would have to compare the contents to see.