Thread: [Fremantle] Android inside chroot
View Single Post
wicket's Avatar
wicket is offline wicket
2014-03-20 , 02:38
Posts: 634 | Thanked: 3,266 times | Joined on May 2010 @ Colombia
#23
Originally Posted by marmistrz View Post
Can't our Linux kernel take care of whole power management and our Dalvik app just let be controlled?
That's a possibility but I wouldn't worry about that right now. Just get something working first.

Originally Posted by lexik View Post
Correct me if I'm wrong, but yes, as we are not emulating anything. Drivers are still needed inside (and outside) the LXC, because chrooted system has no knowledge about it's HW.
Spot on.

Originally Posted by Android_808 View Post
AIUI, LXC containers share the same kernel still - see Oracle documentation on LXC
Correct.

Originally Posted by Android_808 View Post
In that case your now looking at patching host kernel to enable Android, which I dare say is going to break a few things a long the way.
That was always going to be the situation, even with a normal chroot. It's not possible to run multiple kernels without a hypervisor.

Originally Posted by Android_808 View Post
If that's the case I'd start looking at a Sailfish approach by running libhybris, if only for the possibility of detaching MCE and co from N900 specifics to allow porting to other devices.
libhybris shouldn't be needed. The kernel and drivers will be running under Maemo with glibc and will continue to talk to the hardware as normal.

Originally Posted by Android_808 View Post
Problem is how much RAM and performance loss your going to see.
The big advantage of OS-level virtualisation is that there is little or no overhead. It will only use whatever is normally used by Android.

Originally Posted by taixzo View Post
If the container has the same kernel, does that mean it has to load two sets of drivers for everything? Or are the android drivers only loaded inside the LXC container?
Drivers (kernel modules) are an extension to the kernel hence they will be provided (shared) by the host OS. If there are any userspace drivers they would have to be loaded inside the container.

Originally Posted by Alecsandru View Post
and why the drivers (the camera one and others ) were patched to work in android(jolla) if they share the same kernel , i don°t think they share the same drivers
I'm not familiar with Android/Jolla patches and without knowing the details I can only speculate but it's possible that they were userspace drivers.

Originally Posted by Alecsandru View Post
by the way why alien dalvik won°t run on kernels prior to 3.x.x (jolla , leaving qualcomm s**t aside) , from what I remember it was demoed on n900 , that phone was with a updated kernel? or our kernel was patched?
That demo was a long time ago so it would have been based on an older version of Android running a 2.6 kernel, most likely patched.
__________________
DebiaN900 - Native Debian on the N900. Deprecated in favour of Maemo Leste.

Maemo Leste for N950 and N9 (currently broken).
Devuan for N950 and N9.

Mobile devices with mainline Linux support - Help needed with documentation.

"Those who do not understand Unix are condemned to reinvent it, poorly." - Henry Spencer
 

The Following 3 Users Say Thank You to wicket For This Useful Post: