On 12/15/2010 2:51 AM, Pallala, Ramakrishna wrote:
what is the bug number against the firmware? When will the firmware be
fixed?
#define BATT_INTR_SRAM_ADDR 0xFFFF7FC3
#define BATT_OCV_SRAM_ADDR 0xFFFF3008
These address are architectural they will not change across Medfield platforms.
Can I
hard code
These addresses based on the point that they will not change?
If not, I have to request the FW team to provide an IPC call to get these
addresses.
why an IPC call and not a PCI bar ?
Battery driver is a platform device...
and it has a unique sram all to itself????
or is it a global shared sram and it just has a few bytes in it
(I'm fine with #defining an offset within a global sram in a driver..
just not fine with #defining the address of the sram like this)
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
