Carsten, David and Robin,
Thank you very much for this proposal and work already done and started. This
single post alone convinces me that we have not wasted any work on MeeGo (ce),
and that it in fact will have bright future ahead, no matter of the name of the
project , the products based on
Moro,
In fact we have someone already looking into it ;)
Tommi Keisala is working on it now, but naturally it will
Take couple of days before we have anything concrete.
But I think that Juha can work based on Gypsy or whatever is
The MeeGo API atm. Our work will be below that anyway.
Br,
//
Hello all,
[Disclaimer: I don't know Jarkko Moilanen or hardly anyone from uta.fi, but I
do know many people from tut.fi ]
>From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of
>ext Julien Fourgeaud [jul...@lecatalyst.com]
>Sent: Tuesday, November 30, 2010 12:47 AM
>
>On
I have understood that glxgears is opengl program, NOT opengles.
Arjan, are we supposed to have opengl as part of ivi spec ?
Br,
//Harri
From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of
ext Jalics, Laci [laci.jal...@delphi.co
>>From: Arjan van de Ven [ar...@linux.intel.com]
>>Sent: Tuesday, October 26, 2010 10:24 PM
>On 10/26/2010 12:18 PM, Quim Gil wrote:
> On Mon, 2010-10-25 at 23:52 +0200, ext Thiago Macieira wrote:
>> This is why I was wondering why we're not using hardfp *now* for 1.1.0.
>>
>> We shouldn't be brea
>From: Thiago Macieira [thi...@kde.org]
>Sent: Tuesday, October 26, 2010 12:52 AM
>
>On Monday, 25 de October de 2010 17:35:48 Arjan van de Ven wrote:
>> this is me, one of the MeeGo architects, opposing breaking the MeeGo API
>> this lightly.
>> MeeGo's value proposition is about giving a consist
>
>From: Arjan van de Ven [ar...@linux.intel.com]
>Sent: Monday, October 25, 2010 4:59 PM
>
>On 10/25/2010 4:06 AM, jarmo.k...@nokia.com wrote:
>> Hi,
>> We have discussed about hardfp (and other) support in the toolchain team.
>>Current assumption is that h
>
>From: Thiago Macieira [thi...@kde.org]
>Sent: Saturday, October 23, 2010 6:48 PM
>
>> Harri:
>> I propose, that we don't specify softfp as the baseline for complience,
>> but rather say that current softfp is temporary phase and we will move
>> to hardfp a
Hello all,
>
>From: Thiago Macieira [thi...@kde.org]
>Sent: Wednesday, October 20, 2010 8:59 AM
>
>On Wednesday 20. October 2010 07.49.07 Carsten Munk wrote:
>> Line 72, we really need to spell out that it is ARMv7, EABI, softfp
>> (for 1.1) as there is emerg
Dave & all,
Sorry that this came bit from behind trees, I was supposed to have blog post
done some time before this to explain it bit.
But really, like Quim said, there is nothing new on this if you take a look to
what Carsten has already done for N900 and for MeeGo in general.
My name has bee
Hello,
As Auke said, N900 tech spec would practically be the lowest for usable MeeGo
experience.
That is not so bad, knowing that it is already one year old device and based on
bit older hw.
We have still some unused tricks to make it bit faster and usable, but the good
reference
to todays de
Arjan & all,
If I remember correctly some F2F discussions on this topic (on a place close to
Espoo), december deadline is not valid for those components that we are
specifically developing for MeeGo 1.2, like QtMobility 1.2 in question.
If it is not obvious already, this QtM release is designed
Hello,
During Finnish holiday season (July) the following acting roles are
set to secure efficient "MeeGo on N900" execution:
Ameay Palande is acting Team leader for N900 hardware adoption.
-
Carsten Munck is Acting N900
Hello Meegos,
As you know, yesterday Handset UX developement was opened in MeeGo. As N900 is
the other hanset reference device in MeeGo, we are of course actively
developing all the required adaptation elements to make it possible to run
MeeGo Handset UX on N900.
>From N900 adaptation point o
Hello,
One of the problems that we had in last few days was that we had some build
problems under ubuntu.
This one looks different, but I can't say now if they are related or not.
At least at the moment that file is available behind that URL.
Br,
//Harri
From:
Hello,
There will be more information tomorrow how to get image for N900.
We forgot to do one simple thing in time after some hassle, blaim
me if you want to.
But, please remember that this is Day 1 image, Work In Progress.
So don't set your expectations too high.
Openess of the image is on the
Hello,
As decided in our meeting last week, we will have meeting tomorrow, monday
(/sunday evening PDT) about remaining issues for N900 May release. Would be
nice if Intel (kernel) folks can also join to give their view/opinnion.
Meeting is held in #meego-meeting on irc.freenode.net at monday
Hello,
Sorry for short notice, but we will have our first open N900 project meeting
tomorrow at 9.00 EEST (8.00 CEST, 6.00 UTC, 24.00 PDT)
The place is #meego-meeting IRC channel on irc.freenode.net
See also http://wiki.meego.com/ARM/N900
For Agenda etc.
(please notify me if you want to h
>From: meego-dev-boun...@meego.com
>On Behalf Of ext Marko Saukko
>Sent: 17. toukokuuta 2010 10:46
>
>> * If we have some standard items on the agenda for each meeting.
>I think that the current blockers for the next N900 release
>should be discussed to ensure that each of them would be
>handled
>Marko Saukko
>On Wed, May 12, 2010 at 10:09 AM, Carsten Munk
> wrote:
>> So, one of the approaches to open development we're trying
>in the N900
>> team is public synchronisation meetings, described at
>> http://wiki.meego.com/ARM/N900#Team_synchronisation_meetings
>>
>> To get initially start
Hello,
>
>From: Dave Neary [nea...@gmail.com] On Behalf Of ext Dave Neary
>[dne...@maemo.org]
>
>My question (based on the web page, and indeed your answer here) is what
>functionality has been sacrificed in the name of freedom - that is, if
>someone wanted
>From: carsten.m...@gmail.com [carsten.m...@gmail.com] On Behalf Of ext Carsten
>Munk [cars...@maemo.org]
>2010/5/11 wrote:
>> As reasoning from Arjan sounds good, we obviously
>> now need to do some testing with N900 & Btrfs as well.
>>
>> While filesystem is perhaps not something that must be
Ok,
Somehow I forgot this Btrfs thing, I remember that
there was some discussion about it at some point.
As reasoning from Arjan sounds good, we obviously
now need to do some testing with N900 & Btrfs as well.
While filesystem is perhaps not something that must be
the same between devices, it
Hello Meego's,
As indicated in my previous mail about "MeeGo for N900" status, we were
planning to open up our MeeGo work around N900. Now I am happy to announce,
that we are there ;)
First, to make it absolute clear for everybody: This is about open MeeGo
adaptation to N900 device.
Like any o
From: Arnaud Ebalard [a...@natisbad.org]
Sent: Friday, April 23, 2010 10:34 AM
> writes:
>> We have already enabled most of the main drivers, like LCD, GFX, Wlan
>> and BT. Still, there is a lot to do in order to enable .33 on N900,
>> like audio drivers, and modem subsystem including SSI buss dri
Hello MeeGos !
This is brief status update of "MeeGo to N900" project. This project is
currently running as Nokia project, and I am Nokia project lead for it. The
current closed mode of development is not the target for us at all, but rather
transitional condition. As already discussed by Valt
On 4/21/2010 13:50, Arjan van de Ven wrote
>On 4/21/2010 0:22, Roger Quadros wrote:
>> ext Arjan van de Ven wrote:
>> Currently config-generic is more x86 specific it even has ARCH=x86.
>> so currently config-generic is broken.
>
>so fix it ? But what you mention is not broken. It's by design.
>con
That is a great post for 4 year old, he clearly desires to work on Meego in
coming years !
And the mathematical part must include some secret info about Meego schedules ;)
//Hah
From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] On Behalf Of
28 matches
Mail list logo
