Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 3 days, 7 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 4 days, 2 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 6 days, 11 hrs ago - more...
|
2010-05-01
, 13:47
|
|
Posts: 5,335 |
Thanked: 8,187 times |
Joined on Mar 2007
@ Pennsylvania, USA
|
#42
|
The thread "maemo 5 on netbook?" with one post has been merged into this thread.
|
|
2010-05-10
, 18:39
|
|
Posts: 120 |
Thanked: 33 times |
Joined on Jan 2010
|
#43
|
As the title says, is it possible to port Maemo 5 to the Nexus One hardware?
My brother has a Nexus One while I have an N900. I would like to see Android running on my device while he would like to see Maemo running on his.
Any suggestions about how to go about porting Maemo 5 to Nexus One?
My brother has a Nexus One while I have an N900. I would like to see Android running on my device while he would like to see Maemo running on his.
Any suggestions about how to go about porting Maemo 5 to Nexus One?
|
|
2010-05-10
, 18:44
|
|
Posts: 159 |
Thanked: 49 times |
Joined on Jan 2010
|
#44
|
i'm sure it's possible. just don't think there is much demand for porting maemo to the nexus one.
|
|
2010-05-10
, 18:53
|
|
Posts: 120 |
Thanked: 33 times |
Joined on Jan 2010
|
#45
|
Originally Posted by bxbomber
Yes agreed. Amongst the developers there does not seem to be much interest.
i'm sure it's possible. just don't think there is much demand for porting maemo to the nexus one.
I saw this request on xda-developers forum as well but again, it needs at least one developer who's willing to make the effort.
Personally, I don't know anything about porting an OS otherwise I'd certainly try.
It may help though if someone could point us in the right direction, then I can pass the info on to xda.
|
|
2010-05-10
, 18:59
|
|
Posts: 5,335 |
Thanked: 8,187 times |
Joined on Mar 2007
@ Pennsylvania, USA
|
#46
|
The thread "Possible to port Maemo 5 to Nexus One hardware?" with three posts has been merged into this thread.
 |
|
2010-05-11
, 00:52
|
|
Posts: 337 |
Thanked: 283 times |
Joined on Nov 2009
@ NYC
|
#47
|
Mer on Archos:
http://forum.archosfans.com/viewtopic.php?f=34&t=33129
http://www.slashgear.com/archos-5-ge...video-1084946/
So, in answer to the OP, yes.
http://forum.archosfans.com/viewtopic.php?f=34&t=33129
http://www.slashgear.com/archos-5-ge...video-1084946/
So, in answer to the OP, yes.
__________________
In anticipation of TMO's obsolescence, and hoping to meet you all again: elsewhere on the interwebs, I am Dr Doppio.
In anticipation of TMO's obsolescence, and hoping to meet you all again: elsewhere on the interwebs, I am Dr Doppio.
 |
|
2010-05-11
, 11:33
|
|
Posts: 1,716 |
Thanked: 3,007 times |
Joined on Dec 2009
@ Warsaw, Poland
|
#48
|
Is there any mobile platform with open 3D drivers?
After some research of most common Android hardware I found that nor Qualcomm MSM7200A, nor Samsung S3C6410 chips have open 3D driver available.
Lack of 3D is a showstopper for porting Maemo 5 (as N810 owners sadly found out).
After some research of most common Android hardware I found that nor Qualcomm MSM7200A, nor Samsung S3C6410 chips have open 3D driver available.
Lack of 3D is a showstopper for porting Maemo 5 (as N810 owners sadly found out).
__________________
smoku @xiaoka.com (SMTP/XMPP) ...:.:....:... pebbled . Poky Fish : sixaxis . psx4m . uae4all
Jolla Phone post-mortem . . . . . . . . . . -> 1+1 VGN-UX390N
smoku @xiaoka.com (SMTP/XMPP) ...:.:....:... pebbled . Poky Fish : sixaxis . psx4m . uae4all
Jolla Phone post-mortem . . . . . . . . . . -> 1+1 VGN-UX390N
|
|
2010-05-14
, 22:48
|
|
Posts: 1,716 |
Thanked: 3,007 times |
Joined on Dec 2009
@ Warsaw, Poland
|
#49
|
Motorola XT701 might be a target. It's based on Cortex A8.
__________________
smoku @xiaoka.com (SMTP/XMPP) ...:.:....:... pebbled . Poky Fish : sixaxis . psx4m . uae4all
Jolla Phone post-mortem . . . . . . . . . . -> 1+1 VGN-UX390N
smoku @xiaoka.com (SMTP/XMPP) ...:.:....:... pebbled . Poky Fish : sixaxis . psx4m . uae4all
Jolla Phone post-mortem . . . . . . . . . . -> 1+1 VGN-UX390N
|
|
2010-05-14
, 23:22
|
|
Posts: 71 |
Thanked: 36 times |
Joined on Nov 2009
@ CT, USA
|
#50
|
I'm not that experience with Android myself, but there was some interesting stuff written recently with the spat between the kernel maintainers and the Android team about removal of the source from the staging tree.
So it's mostly a standard kernel with some out of tree patches. I believe the dispute was resolved and Google/OHA have promised to work to get the patches back into mainline. But it appear that the biggest problem is drivers (not surprisingly); maybe dj_steve has some perspective on this based on this nitdroid experience?
The Android kernel code is more than just the few weird drivers that were in the drivers/staging/android subdirectory in the kernel. In order to get a working Android system, you need the new lock type they have created, as well as hooks in the core system for their security model.
In order to write a driver for hardware to work on Android, you need to properly integrate into this new lock, as well as sometimes the bizarre security model. Oh, and then there's the totally-different framebuffer driver infrastructure as well.
This means that any drivers written for Android hardware platforms, can not get merged into the main kernel tree because they have dependencies on code that only lives in Google's kernel tree, causing it to fail to build in the kernel.org tree.
Because of this, Google has now prevented a large chunk of hardware drivers and platform code from ever getting merged into the main kernel tree. Effectively creating a kernel branch that a number of different vendors are now relying on.
Now branches in the Linux kernel source tree are fine and they happen with every distro release. But this is much worse. Because Google doesn't have their code merged into the mainline, these companies creating drivers and platform code are locked out from ever contributing it back to the kernel community. The kernel community has for years been telling these companies to get their code merged, so that they can take advantage of the security fixes, and handle the rapid API churn automatically. And these companies have listened, as is shown by the larger number of companies contributing to the kernel every release.
source:http://www.kroah.com/log/linux/andro...html?seemore=y
just saw someone flash a netbook that was using windows ce with the android os. it got me to thinking....can we use maemo5 os on a netbook? and if so...where do we start in order to do this?