[Fremantle] Android inside chroot - Page 6 - maemo.org

Active Topics

Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 2 days, 17 hrs ago
more...

Page 6 of 8

« First

< Prev

Next >

Thread Tools

	Alecsandru	2014-03-23 , 12:37
	Posts: 439 \| Thanked: 282 times \| Joined on Oct 2012	#51

"You’ll need a kernel with the Android patches (binder, ashmem, logger etc.)"
power_management : CONFIG_PM=y
CONFIG_HAS_EARLYSUSPEND=y
CONFIG_SUSPEND=y
wakelocks : CONFIG_HAS_WAKELOCK=y
CONFIG_WAKELOCK=y
CONFIG_EARLYSUSPEND=y
CONFIG_USER_WAKELOCK=y
CONFIG_FB_EARLYSUSPEND=y
ashmem : CONFIG_ASHMEM=y
pmem : CONFIG_ANDROID_PMEM=y
switch class support : CONFIG_SWITCH=y
staging drivers : CONFIG_STAGING=y
CONFIG_ANDROID=y
binder : CONFIG_ANDROID_BINDER_IPC=y
logger : CONFIG_ANDROID_LOGGER=y
ram console : CONFIG_ANDROID_RAM_CONSOLE=y
usb_gadgets with at least adb selected - CONFIG_USB_GADGET=y
CONFIG_USB_ANDROID=y
CONFIG_USB_ANDROID_ACM=y
CONFIG_USB_ANDROID_ADB=y
CONFIG_USB_ANDROID_MASS_STORAGE=y
CONFIG_USB_ANDROID_MTP=y
power supply : CONFIG_POWER_SUPPLY=y
CONFIG_PDA_POWER=y

these are required for android kernel , what do we have , and what do we need?

__________________

N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version

Quote & Reply |

The Following 2 Users Say Thank You to Alecsandru For This Useful Post:
lexik, nokiabot

	wicket	2014-03-24 , 05:37
	Posts: 634 \| Thanked: 3,266 times \| Joined on May 2010 @ Colombia	#52

Originally Posted by foobar

I'd say help freemangordon, pali, et al. to run maemo on 3.x kernels, then go from there.
Win-win for everyone.

I'd also rather see everyone chime together to work on the 3.x kernel, however the reality is that not everyone is a kernel hacker. Their kernel is already quite usable so it should be suitable for initial testing.

Originally Posted by Alecsandru

that it°s a longshoot , it should be more easy to apply to our kernel instead of the 3.x.x one due to missing drivers in the last one

I doubt it. Android has been bootable with a vanilla kernel since Linux 3.3.

Originally Posted by Alecsandru

"You’ll need a kernel with the Android patches (binder, ashmem, logger etc.)"
power_management : CONFIG_PM=y
CONFIG_HAS_EARLYSUSPEND=y
CONFIG_SUSPEND=y
wakelocks : CONFIG_HAS_WAKELOCK=y
CONFIG_WAKELOCK=y
CONFIG_EARLYSUSPEND=y
CONFIG_USER_WAKELOCK=y
CONFIG_FB_EARLYSUSPEND=y
ashmem : CONFIG_ASHMEM=y
pmem : CONFIG_ANDROID_PMEM=y
switch class support : CONFIG_SWITCH=y
staging drivers : CONFIG_STAGING=y
CONFIG_ANDROID=y
binder : CONFIG_ANDROID_BINDER_IPC=y
logger : CONFIG_ANDROID_LOGGER=y
ram console : CONFIG_ANDROID_RAM_CONSOLE=y
usb_gadgets with at least adb selected - CONFIG_USB_GADGET=y
CONFIG_USB_ANDROID=y
CONFIG_USB_ANDROID_ACM=y
CONFIG_USB_ANDROID_ADB=y
CONFIG_USB_ANDROID_MASS_STORAGE=y
CONFIG_USB_ANDROID_MTP=y
power supply : CONFIG_POWER_SUPPLY=y
CONFIG_PDA_POWER=y

these are required for android kernel , what do we have , and what do we need?

You can easily find that out by grepping the kernel .config file for each option.

__________________
~~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

Quote & Reply |

The Following User Says Thank You to wicket For This Useful Post:
foobar

lexik	2014-03-24 , 09:54
Posts: 71 \| Thanked: 177 times \| Joined on Aug 2013	#53

Originally Posted by Alecsandru

"You’ll need a kernel with the Android patches (binder, ashmem, logger etc.)"
power_management : CONFIG_PM=y
CONFIG_HAS_EARLYSUSPEND=y
CONFIG_SUSPEND=y
wakelocks : CONFIG_HAS_WAKELOCK=y
CONFIG_WAKELOCK=y
CONFIG_EARLYSUSPEND=y
CONFIG_USER_WAKELOCK=y
CONFIG_FB_EARLYSUSPEND=y
ashmem : CONFIG_ASHMEM=y
pmem : CONFIG_ANDROID_PMEM=y
switch class support : CONFIG_SWITCH=y
staging drivers : CONFIG_STAGING=y
CONFIG_ANDROID=y
binder : CONFIG_ANDROID_BINDER_IPC=y
logger : CONFIG_ANDROID_LOGGER=y
ram console : CONFIG_ANDROID_RAM_CONSOLE=y
usb_gadgets with at least adb selected - CONFIG_USB_GADGET=y
CONFIG_USB_ANDROID=y
CONFIG_USB_ANDROID_ACM=y
CONFIG_USB_ANDROID_ADB=y
CONFIG_USB_ANDROID_MASS_STORAGE=y
CONFIG_USB_ANDROID_MTP=y
power supply : CONFIG_POWER_SUPPLY=y
CONFIG_PDA_POWER=y

these are required for android kernel , what do we have , and what do we need?

alex@aexbook:~/NeoDroid/maemo-kernel$ fgrep -x -f droid.config .config
CONFIG_SUSPEND=y

^ this, in default make rx51_defconfig generated .config file, just with following N900 specific options enabled:

CONFIG_ARM_APPENDED_DTB=y
CONFIG_ARM_ATAG_DTB_COMPAT=y
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_EXTEND=y
CONFIG_PINCTRL_SINGLE=y
CONFIG_REGULATOR_TWL4030=y
CONFIG_REGULATOR_FIXED_VOLTAGE=y

Last edited by lexik; 2014-03-24 at 10:12.

Quote & Reply |

The Following 2 Users Say Thank You to lexik For This Useful Post:
foobar, nokiabot

	wicket	2014-03-24 , 19:23
	Posts: 634 \| Thanked: 3,266 times \| Joined on May 2010 @ Colombia	#54

Originally Posted by lexik

alex@aexbook:~/NeoDroid/maemo-kernel$ fgrep -x -f droid.config .config
CONFIG_SUSPEND=y

Your grep is matching the whole line (-x). Based on your output, I'm assuming that your droid.config file contains entries that only check what is enabled. Options that may be available but aren't enabled by default won't be included.

This is what I get when grepping the 3.x N900 kernel config:

Code:

$ for i in CONFIG_{PM,HAS_EARLYSUSPEND,SUSPEND,HAS_WAKELOCK,WAKELOCK,EARLYSUSPEND,USER_WAKELOCK,FB_EARLYSUSPEND,ASHMEM,ANDROID_PMEM,SWITCH,STAGING,ANDROID,ANDROID_BINDER_IPC,ANDROID_LOGGER,ANDROID_RAM_CONSOLE,USB_GADGET,USB_ANDROID,USB_ANDROID_ACM,USB_ANDROID_ADB,USB_ANDROID_MASS_STORAGE,USB_ANDROID_MTP,POWER_SUPPLY,PDA_POWER}; do grep -E "$i\W" .config > /dev/null && echo +$i || echo -$i; done
+CONFIG_PM
-CONFIG_HAS_EARLYSUSPEND
+CONFIG_SUSPEND
-CONFIG_HAS_WAKELOCK
-CONFIG_WAKELOCK
-CONFIG_EARLYSUSPEND
-CONFIG_USER_WAKELOCK
-CONFIG_FB_EARLYSUSPEND
-CONFIG_ASHMEM
-CONFIG_ANDROID_PMEM
-CONFIG_SWITCH
+CONFIG_STAGING
+CONFIG_ANDROID
-CONFIG_ANDROID_BINDER_IPC
-CONFIG_ANDROID_LOGGER
-CONFIG_ANDROID_RAM_CONSOLE
+CONFIG_USB_GADGET
-CONFIG_USB_ANDROID
-CONFIG_USB_ANDROID_ACM
-CONFIG_USB_ANDROID_ADB
-CONFIG_USB_ANDROID_MASS_STORAGE
-CONFIG_USB_ANDROID_MTP
+CONFIG_POWER_SUPPLY
+CONFIG_PDA_POWER

'+' indicates that the option can be enabled in the kernel.
'-' indicates that the option is not available and would need patching in the kernel. Note that not all of these may be required for running under a chroot/container.

[EDIT]
This list isn't entirely accurate. Some of those options which I have marked as unavailable are actually available but are not present in the default .config file. They get added automatically when you enable a dependent option. Sorry about that.
[/EDIT]

You may find these links useful:
http://community.arm.com/groups/andr...r-arm-platform
http://www.elinux.org/Android_on_OMAP

Last edited by wicket; 2014-04-21 at 03:28.

Quote & Reply |

The Following 4 Users Say Thank You to wicket For This Useful Post:
ceteigrek, lexik, nokiabot, reinob

	Alecsandru	2014-03-25 , 01:57
	Posts: 439 \| Thanked: 282 times \| Joined on Oct 2012	#55

the purpose is to make the maemo OS to use android aplications , no to make from maemo nitdroid(no calls , gps ,etc etc) ,I was reffering to the mising drivers in the new kernel for n900 (3.x.x), no at general , our kernel(2.6.28) needs to be patched at least until 3.x.x fully support n900(here is the longshoot) , and we know about PM , the next step is to find someone with the skills to patch kernel and after flashing the new kernel , maemo needs to be alive at boot

__________________

N900 Beast featuring :
8GB OPTFS@ext4(*performance mount options)
overclock: cpu[125 - 1,150(*VDD1)+Dsp overclock
CSSU-T latest version

Last edited by Alecsandru; 2014-03-25 at 02:04.

Quote & Reply |

seanmcken	2014-04-21 , 03:09
Posts: 863 \| Thanked: 213 times \| Joined on Feb 2012 @ Goa	#56

any developements here?

Quote & Reply |

	Sohil876	2014-04-21 , 10:15
	Posts: 130 \| Thanked: 132 times \| Joined on Jan 2013 @ India	#57

someone managed to compile lxc for maemo? Upload here please.

Quote & Reply |

pierrem	2014-04-21 , 10:28
Posts: 107 \| Thanked: 173 times \| Joined on Feb 2011	#58

Originally Posted by Sohil876

someone managed to compile lxc for maemo? Upload here please.

LXC requires at least linux kernel 3.14 to be secure.
I don't know if someone manage to port specific N900 code to this kernel version, but if not, there is no way to have LXC for maemo.

Any way, to stay on topic, and, as it has certainly already been said above (did not check), a chroot, more over a super chroot such as LXC, is not a solution to run Android, since the point of a chrooted system is to use the host kernel with the user environment of the guest.
And as far as I know, Android kernel features are not integrated in the linux kernel yet.

So, that makes two reasons why LXC won't be a solution for android, at least for now

Quote & Reply |

The Following 2 Users Say Thank You to pierrem For This Useful Post:
Estel, nokiabot

lexik	2014-04-21 , 16:58
Posts: 71 \| Thanked: 177 times \| Joined on Aug 2013	#59

Originally Posted by seanmcken

any developements here?

I'm having my fun with kernel stuff. Nothing interesting (at least for now) .. but yes, this project is totally alive

Quote & Reply |

The Following 3 Users Say Thank You to lexik For This Useful Post:
nokiabot, OVK, seanmcken

liar	2014-04-21 , 17:11
Posts: 210 \| Thanked: 841 times \| Joined on Feb 2013	#60

Originally Posted by marmistrz

Dalvik links against kernel modules? So how would have thp launched a Dalvik hello world without Android kernel modules?

Yes, pm = power management.

thp used the nitdroid dual boot kernel which has all necessary android modules included

Quote & Reply |

The Following 5 Users Say Thank You to liar For This Useful Post:
Estel, lexik, marmistrz, nokiabot, seanmcken

Page 6 of 8

« First

< Prev

Next >

Active Topics

Firefox with Leste (10)