View Single Post
Old 08-25-2012, 10:39 AM   #76
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
@ Hawhill

Devices (well, device registers) are memory mapped . . .
When the iROM code starts, there is a single, 32bit, identity mapping installed in the TLB . . .
The iROM code can read (and write) memory locations . . .

If the battery management chip's "battery charge level" address can be found, it might be possible to read the battery charge level before continuing with the download of the "RAM kernel".

If it is mapped into the higher 60Gbytes of the address space, then another TLB entry would have to be made to read it.

This would give the application a chance to advise the user if the K3's battery should be re-charged before continuing.

- - - -

I seem to recall seeing battery level check messages in the kernel's dmesg listing during boot.
If so, it might be possible to find that "battery charge level" address in the (Amazon patched) kernel source code.

I'll PM you the details if I stumble across them, but don't wait on me, I may never stumble on them.
knc1 is offline   Reply With Quote