Adding meego-architecture to the Cc list...
Regarding the use of contextkit in MeeGo, someone should define what properties
the "OS" publishes through contextkit (if any). This set of properties would
then become the set that all MeeGo instances would need to support. Depending
on other MeeGo a
Hi,
The non-graphical feedback framework, NGF, coming in MeeGo 1.2 (see the
attached mail) is meant for notification/alert type vibra playback. The idea is
that the NGF defines the interface for adaptation in this area (and NGF should
have a plugin architecture suitable for this). Whatever SW c
In the meanwhile, a few smaller comments to 1.0.99.3:
- Lines 121, 122: "...but changes MUST NOT affect API, ABI, or behavior."
- Should this say something like "in incompatible manner". Meaning,
can someone e.g. add a function to some API for their own use?
- 2.5: Do we need som
Still waiting for other comments concerning whether some packages now in the
MeeGo Core Packages list contain components that are not applicable in all
MeeGo HW/device environments...
Anyway, I agree with point (2) below. Generally, if the compliance requirements
are expressed as they now are,
Hmmm, don't know any details in this area, so just checking... In MeeGo the
Sensor Framework itself must be _generic_ and fully open source I believe.
Sensor HW adaptation (including adaptor plugins in the Sensor Framework),
however, can contain proprietary stuff. So is there some refactoring ne
The idea, to my understanding, has been that HW specifics in this area would be
hidden behind CameraBin...
Regards, Jari
> -Original Message-
> From: Shin Minjung (Nokia-MS-Qt/Brisbane)
> Sent: 03. marraskuuta 2010 17:11
> To: ext Teemu Tuominen; Palojarvi Jari (Nokia-MS/Tampere)
> Cc: m
Hi,
Just took a look at 1.0.99.3. I'd like to point out one potential issue related
to System Implementation / Platform Compliance and the MeeGo Core Packages list.
If all compliant platforms must include the binary packages listed in the MeeGo
Core Packages list, I suppose that all SW compone
Just a quick note highlighting the obvious: the camera source component in
GStreamer and the subdev drivers are a part of camera HW adaptation. So they
may (and likely will) differ between different HW platforms.
Regards, Jari
> -Original Message-
> From: meego-dev-boun...@meego.com [ma
As Dawn writes below, please notice that we now have a new mailing list for all
those who are trying to port MeeGo to some new HW environment AND those who
might know how to help these people. So if you feel that you belong to either
one of these groups, join the list...
Regards, Jari
> -O
Hi,
To my understanding the MeeGo.com builds are for ARMv7. To compile for ARMv6, I
would think that you need to have your own OBS that links to the MeeGo.com OBS
+ the necessary ARMv6 tool chain integrated to your own OBS. There's one link
to OBS installation instructions on the MPG page. Othe
Don't know the schedules but I wouldn't make any final conclusions just based
on the 1.1 release content. Things may change after that.
Regards, Jari
From: ext Jarmo Kuronen [mailto:jarmo.kuro...@symbio.com]
Sent: 14. syyskuuta 2010 09:43
To: Palojarvi Jari (Nokia-MS/Tampere)
Cc: meego-dev@meego
This is my view, too. Basically the key point of GeoClue would be to offer an
agreed (low level) C API to the location services in MeeGo OS. The Qt Mobility
location API back-end could be written on top of that but would not have to be
(e.g. if that would be an issue from performance perspective
Standardizing a low(er) level C API to each middleware level “service” in MeeGo
OS would have two benefits:
- A single Qt Mobility API backend implementation would suffice
=> no need for vendor specific implementations
- There would be a standard way to integrate middleware level
SW componen
Hi,
Some information and pointers here: http://wiki.meego.com/MeeGo_Porting_Guide
Regards, Jari
> -Original Message-
> From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
> On Behalf Of ext Sah, Shitij IN BLR SISL
> Sent: 13. syyskuuta 2010 15:58
> To: meego-dev@meego
Hi,
> Does this mean that there will be no "generic" policy enforcement support for
> example to PulseAudio but All adaptations will roll-out their own PulseAudio
> enforcement modules from scratch?
No. I just don't know enough details to say how this goes in reality at this
point. Naturally i
In my opinion, a meego-porting mailing list would be a good idea. Dawn (and
others) - any thoughts about this?
Regards, Jari
From: ext USA Linux UAE [mailto:usasoftwareengin...@gmail.com]
Sent: 10. syyskuuta 2010 15:46
To: Jarmo Kuronen
Cc: Palojarvi Jari (Nokia-MS/Tampere); meego-dev@meego.com
Hi all,
I've now spent some more time creating content to the MeeGo Porting Guide
(http://wiki.meego.com/MeeGo_Porting_Guide). All that it now needs is readers
:-). Please take a look and give your comments/suggestions etc. on the
associated discussion page. The content should be least roughly
Very good proposals. If you or someone else has the time and knowledge, feel
free to start entering content to the page. And you can change the outline as
required as well.
Regards, Jari
> -Original Message-
> From: carsten.m...@gmail.com [mailto:carsten.m...@gmail.com] On Behalf
> Of e
Hi all,
Just as an ad, there's now some initial concrete information at
http://wiki.meego.com/MeeGo_Porting_Guide (under Display and graphics, Media,
Communications and Sensors). Nothing "huge" but at least something the start
from.
Regards, Jari
> -Original Message-
> From: meego-de
OK, will change that.
Regards, Jari
> -Original Message-
> From: Boudra Fathi (Nokia-D/Helsinki)
> Sent: 22. kesäkuuta 2010 14:53
> To: Palojarvi Jari (Nokia-D/Tampere); meego-dev@meego.com
> Subject: RE: [MeeGo-dev] Porting meego to new hardware
>
> Hi,
>
> > there's a draft table of
Hi again,
I've been mostly looking at the SW architecture issues when it comes to porting
MeeGo to new environments, so I'm not so well aware of the process issues and
expecting someone else to describe those things.
The contacts that you can find from
http://meego.com/about/governance/release
Hi,
Actually some thinking around this has happened already, but somewhat silently
so far. Anyway, there's a draft table of contents for a MeeGo Porting Guide at
http://wiki.meego.com/MPG. I'm planning to update the pages a bit during this
week. In some areas, the HW adaptation SW interfaces ar
22 matches
Mail list logo
