|
|
11-02-2009
, 11:17 AM
|
|
Posts: 54 |
Thanked: 38 times |
Joined on Aug 2009
@ Wrocław / Poland
|
#2
|
|
|
11-02-2009
, 11:25 AM
|
|
Posts: 237 |
Thanked: 167 times |
Joined on Feb 2007
@ Powell, OH
|
#3
|
| The Following User Says Thank You to theflew For This Useful Post: | ||
|
|
11-02-2009
, 11:32 AM
|
|
Posts: 2,152 |
Thanked: 1,488 times |
Joined on Jan 2006
@ Czech Republic
|
#4
|
| The Following User Says Thank You to fanoush For This Useful Post: | ||
|
|
11-02-2009
, 01:57 PM
|
|
Posts: 135 |
Thanked: 160 times |
Joined on Aug 2009
@ Chateauroux, FRANCE
|
#5
|
|
|
11-03-2009
, 10:03 AM
|
|
Posts: 54 |
Thanked: 38 times |
Joined on Aug 2009
@ Wrocław / Poland
|
#6
|
![]() |
| Thread Tools | Search this Thread |
|
sorry to bother with probably already discussed topic, but...
The thing is - e.g. palm pre and motorola droid are based on probably almost the same hardware as the n900 (omap 3430 platform), and they run on webos/android (meaning open source linux kernel + probably source of the rest of their platform too)...
Would it be possible to port maemo to these devices? I'm sure it'd be possible to port Mer - the question is what about closed-source components of Maemo? Are they even "fetchable"? And would it be even legal to use these components? I've again lost the list of closed components - does it also involve the GUI, or is it only stuff like device drivers and some telephony stack stuff..?
thanks for opinions
Andrej