![]() |
2010-05-16
, 20:00
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#72
|
If the libraries are ported (or at least Qt) then it should be very easy to port the applications.
What kind of work is required in order to make Qt accelerated? Is it slow because of the missing 3D? Is there something different in the X environment of MeeGo and that of Diablo that makes these libraries accelerated on MeeGo and slow on Diablo? Isn't it on both places the same good old X?
After Mer I have some doubts that anything usable will come from 'MeeGo_on_N8x0'.
The Following User Says Thank You to Stskeeps For This Useful Post: | ||
![]() |
2010-05-16
, 20:53
|
Posts: 34 |
Thanked: 20 times |
Joined on Jun 2009
@ Bulgaria
|
#73
|
You are free to do the work to support Qt4.6/7 for OS2008 in the Community SSU project or in diablo extras.
This MeeGo hardware adaptation work is to be able to support a modern stack on top of the N8x0 and keep it maintained. MeeGo isn't just Qt. It is a lot of middleware and newer kernels, new libc6 etc. As well as applications built towards this mix.
Hint: our kernel and libc6 on Diablo would cause most apps not to run in their binary ARMv5 form. And those are not easily upgrade-able.
We could be doing backports from now on to the end of time for no good benefit to patchwork on top of a dead-end OS. Not going to do that, personally.
Now, can we get back on topic? This is an effort to provide a hardware adaptation for N8x0 for MeeGo, nothing more, nothing less.
Right, please go take this issue up in my review thread instead. This is a place for development.
![]() |
2010-05-16
, 20:57
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#74
|
1. Make from MeeGo on N8x0 something useful for the users or 2. see what is required for the hardware acceleration of Qt (the system integration is optional).
I think 2. is easier than 1. and it is also more feasible. After Mer I have some doubts that anything usable will come from 'MeeGo_on_N8x0'. If the libraries are ported (or at least Qt) then it should be very easy to port the applications.
The Following User Says Thank You to attila77 For This Useful Post: | ||
![]() |
2010-05-16
, 21:16
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#75
|
And I proposed and easier way to provide the users with MeeGo experience.
![]() |
2010-05-18
, 03:11
|
Posts: 7 |
Thanked: 2 times |
Joined on May 2010
@ California
|
#76
|
The Following User Says Thank You to morr22066 For This Useful Post: | ||
![]() |
2010-05-18
, 21:29
|
|
Posts: 1,137 |
Thanked: 402 times |
Joined on Sep 2007
@ Catalunya
|
#77
|
It would be VERY helpful if there were a section organized and tabbed under headings similar to the download section where there could step by step instructions on many of the more useful tips and tricks. Clear instructions on things like cloning, booting from the memory card, etc. Perhaps a shortcut to it could be placed on the page near FAQ, Forums, etc. Then it may be a simple matter to "update" a single set of instructions rather than having multiple sets of instructions which have been revised, changed and updated on multiple threads.
![]() |
2010-05-21
, 12:26
|
Posts: 3 |
Thanked: 0 times |
Joined on Apr 2010
|
#78
|
Added myself as this interests me obviously. I hope to contribute as the stack matures a bit more.
I'd say a useful M1 would be to get all other sensors (wifi, GPS) working: Boots, can connect to the outside world and find where it is in the world.
Interface isn't quite as crucial as something like xfce can be used as an interim until whatever interface meego handset will end up with can be evaluated, so that might be an M2, or M3?
![]() |
2010-05-23
, 17:22
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#79
|
![]() |
2010-05-24
, 22:17
|
Posts: 670 |
Thanked: 367 times |
Joined on Mar 2009
|
#80
|
It boots off external minisd by default - means you can flasher -k -l a kernel and dual-boot to it that way.
![]() |
Tags |
hardware adaptation, meego |
Thread Tools | |
|
I think 2. is easier than 1. and it is also more feasible. After Mer I have some doubts that anything usable will come from 'MeeGo_on_N8x0'. If the libraries are ported (or at least Qt) then it should be very easy to port the applications.
What kind of work is required in order to make Qt accelerated? Is it slow because of the missing 3D? Is there something different in the X environment of MeeGo and that of Diablo that makes these libraries accelerated on MeeGo and slow on Diablo? Isn't it on both places the same good old X?