Hi,
Fortunately the userspace can partially ignore the
charging issue because the RETU (now Betty) chip takes care of that in
the hardware. Charging / charger-cable / power-button / battery-life
states are readable from /sys and /dev.
Hmm where exactly can you read that info from ?
I quickly searched through sysfs, proc and dev but without much luck :-)
The best bet for a distro is probably to leave the maemo "initfs",
which contains closed-source DSME / BME / flasher, in place and let
the custom rootfs run on top of it. If you need some details about
retu / tahvo driving / bootloading, I may be able to tell because I
recently had to poke on it for a different project.
Should I get android to work correctly it would be nice to automatically
start android after booting the n810.
Thus if you have any info on setting up wifi automatically from a script
and what exactly to disable to prevent the system from starting Xomap,
dbus, hal etc... that would be nice :-)
Next would be to try to get the framebuffer driver hacked to work with the
m5 image ... the framebuffer driver doesn't support double buffering thus we
only get a black screen :-(
I understand the userspace is going to be open-source at some point,
which would render this work a bit useless. If it doesn't get
open-sourced then it's a waste of time either way I think?
According to what I've read so far it will be open-sourced as soon as
the first devices start to appear...which probably won't be anytime soon
But even then that work wouldn't be useless because Google won't release
a framebuffer driver for Nokia n800/810 ... so if one wants to be able
to run m5 and future releases, somebody has to modify the current driver
to be compatible with android...if that is even possible.
--
regards,
Georges Toth
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
