View Single Post
Old 10-07-2012, 11:44 AM   #7
geekmaster
Всё гениальное просто.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,070
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
Quote:
Originally Posted by knc1 View Post
There is a basic problem with the recovery process that uses the Freescale provided code.

With the exception of the off-chip RAM and 2 models of USB UARTS, the Freescale code only handles on-chip devices.

The battery charger and management is done off-chip.
Without code to control the off-chip battery management, things are more than a bit non-deterministic.

The good news is the source code license which the ATK is under - it covers derivatives of the client side code (mis-named by Freescale as a "RAM kernel").

The bad news is that same license prohibits the addition of any code that would bring the Freescale provided code into the "Open Source" world. I.E: You can not add GPL licensed code (or any other "viral" license) when making your derivative.

The only known (to me anyway) sources of battery management chip code is GPL licensed.

The solution is to re-write (rather than derive) the client side code so that existing GPL code can be re-used.

In the time I have been posting about this, I have not been exactly over-whelmed by offers of assistance and it is too much of a project for me to do on my own.

Which leaves the end-user with the next-best alternative - remove the battery and re-charge it with an "Amazon approved" charger outside of the Kindle.
Now that you worded it this way you have attracted more of my attention. My problem is not enough time, and I spend far too little of that time in the forums and not in the code. I need to spend more time studying code and manuals, and writing and testing code, and less of it reading and posting here...

But about posting, I want to do a TOTAL REWRITE of the simple debricking method, because now we have much simpler methods, based on things I have though about and wanted to do for a long time, but I never got around to implementing. Now thanks to other devs here who have provided a couple of these tools and methods that I did not get around to doing myself, we have the major critical components to do debricking WITHOUT fastboot, and without MfgTool as well. I need to organize and test and add some glue code to tie all this together, but there will soon be an easier way to debrick/jailbreak/install apps (partly replacing what yifanlu announced he was working on). But it takes time, and I have little now...
geekmaster is offline   Reply With Quote