I don't know the board you are using. But you need to have a AC driver
to register with power_supply_core to create the AC0 or ac directory.
For X86, we drivers/acpi/ac.c. You can also look at
drivers/power/goldfish_battery.c and look for
power_supply_register(&pdev->dev, &data->ac)
Yi
On Mon, 2009-04-27 at 08:03 +0400, Elvis Dowson wrote:
> Hi,
>       The board that I have is an Overo Earth with Palo43 expansion
> board. It has not batteries connected to it. I took a quick look at
> the x86 patches, and it attempts to correct the paths to the actual
> objects. 
> 
> 
> I'm trying to first get the appropriate objects to appear first in the
> power_supply folder. Its empty at the moment.
> 
> 
> Elvis
> 
> On Mon, Apr 27, 2009 at 2:22 AM, Yi Sun <beyo...@gmail.com> wrote:
>         
>         More hints for u; even u enable u drivers, u may still have
>         problems.
>         Do check the content in sys/class/power_supply/ to make sure
>         it has
>         what Android expected.Athe first thing u may need to fix is
>         the paths
>         in com_android_batteryservice.cpp.
>         Please take a look on the X86 patches for detail.
>         It depends on u battery type, u may see even more issues, but
>         most of
>         them are easy to fix and no need to mention here
>         Yi
>         
>         
>         
>         
>         On Apr 26, 2009, at 2:59 PM, Yi Sun <beyo...@gmail.com> wrote:
>         
>         > You need to enable u AC and BAT driver.
>         >
>         >
>         >
>         > On Apr 26, 2009, at 9:37 AM, Elvis Dowson
>         <elvis.dow...@gmail.com>
>         > wrote:
>         >
>         >>
>         >> Hi,
>         >>     I've ported the android-2.6.29 kernel to the Overo
>         linux-
>         >> omap3-2.6.29 kernel version. The android logo boots up, and
>         after
>         >> sometime, the system shuts down.
>         >>
>         >> When I look in the find /sys/class/power_supply folder, I
>         don't see
>         >> anything. I have enabled CONFIG_POWER_SUPPLY=y in my
>         defconfig.
>         >>
>         >> What could be going wrong? Why are the required devices not
>         being
>         >> created?
>         >>
>         >> Best regards,
>         >>
>         >> Elvis
>         >>
>         >> I/SystemServer(  865): Starting Battery Service.
>         >> E/BatteryService(  865): Could not open
>         '/sys/class/power_supply/ac/
>         >> online'
>         >> E/BatteryService(  865): Could not open
>         '/sys/class/power_supply/usb/
>         >> online'
>         >> E/BatteryService(  865): Could not open
>         '/sys/class/power_supply/
>         >> battery/present'
>         >> E/BatteryService(  865): Could not open
>         '/sys/class/power_supply/
>         >> battery/capacity'
>         >> E/BatteryService(  865): Could not open
>         '/sys/class/power_supply/
>         >> battery/batt_vol'
>         >> E/BatteryService(  865): Could not open
>         '/sys/class/power_supply/
>         >> battery/batt_temp'
>         >> E/BatteryService(  865): Could not open
>         '/sys/class/power_supply/
>         >> battery/status'
>         >> E/BatteryService(  865): Could not open
>         '/sys/class/power_supply/
>         >> battery/health'
>         >> E/BatteryService(  865): Could not open
>         '/sys/class/power_supply/
>         >> battery/technology'
>         >>
>         >>
>         >> >>
>         
>         
>         
> 
> 
> 
> > 


--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to