Quote:
Originally Posted by knc1
"All existing programs" includes the programs in the Amazon system image.
|
Yes, that is why they recompiled everything that uses the eink header file instead of fixing that structure in the header file. It locks all recompiled programs to ONLY work with 5.1.x and not with 5.0.x if they need to do eink display updates.
Quote:
Originally Posted by knc1
Perhaps a short note in the de-bricking sticky about always using a matched kernel/system image pair?
|
Done! I added a message at the top of the first post, and again just above the forensic image download link.
Quote:
Originally Posted by knc1
A related question:
Is this e-ink driver a module?
My reasoning -
If it is, then it should be possible to build the new driver module so that it can be loaded into the old kernel (making the old kernel compatible with the new system image).
|
If we load a new kernel mode eink driver, or load a new kernel with kexec, that would make it a bit hard to integrate my native-mode apps with kindlets like I want to (in a client-server arrangement, perhaps communicating via shared files if necessary).
Quote:
Originally Posted by knc1
Just a thought tossed out for someone with time on their hands and a working Kindle kernel build environment.
|
I want to build custom kernels too. Could you please share pointers or links showing what cross-tool versions, headers and librarys I need, etc. ? A link to a little tutorial would be nice to save time experimenting with options. Thanks! (I wish I had more time...)
