On 2010-11-04 at 08:04:02, ext HorryChiang wrote:
>
> The algorithms used with the magnetometer are proprietary, and are not
> included with this build. They can be installed from package sensorfw-
> plugins-compasslogic.
>
> Unless the package is installed, CompassSensor and MagnetometerSensor
On 2010-11-04 at 06:46:16, ext Bintian Wang wrote:
>
> I try to install package "sensorfw-tests" on Aava and CDK, but it
> report dependency error for lacking packages "ci-testing" and
> "mcetools", I search all the meego repo but failed to find these two
> packages, anyone can give me some clu
Dear master,
There is some information about CompassSenosor at
sensorfw-0.6.19.p.git82de2729/debian/README
(sensorfw-0.6.19.p.git82de2729-2.38.src.rpm)
--
###
### The Debian Package sensord
###
This package provides the senso
Hi, all
mic2 0.22.2 is available in http://repo.meego.com/MeeGo/tools/repos/, the
important changes are using find_binary_path to get all the bianry file
paths and adding --include-source for compliance check, 11 bugs are fixed
, the below are all the changes since 0.21.1:
- Fix comps.xml mat
I try to install package "sensorfw-tests" on Aava and CDK, but it report
dependency error for lacking packages "ci-testing" and "mcetools", I search all
the meego repo but failed to find these two packages, anyone can give me some
clues?
Certainly, I can install it with "--nodeps", but I think it
Hi,
We have a new mail list for MeeGo distribution tools, it is a Discussion list
for the MeeGo release team to communication about the tools used in the release
and packaging of the MeeGo distribution. Tools discussed on this list: MeeGo
Image Creator (MIC), Image Manager, spectacle, OBS, BOSS
Hi Niels,
Please subscribe to http://lists.trolltech.com/mailman/listinfo/qt-qml and
you'll find a brewing and knowledgeable community around QML and Qt Quick.
Cross-posting for introductions :)
Cheers,
Henrik
On Nov 3, 2010, at 1:59 PM, ext Niels Mayer wrote:
> [I forgot to send this to meeg
- "Nasa" wrote:
> - "Patrick Ohly" wrote:
>
> > On Mo, 2010-10-25 at 12:12 +0100, Nasa wrote:
> > > I have been somewhat confused on how system upgrading is being
> > handled
> > > for meego. If I install a base meego system (ie: 1.0) and use
> > zypper
> > > (dist-upgrade) to keep
On 11/03/10 10:43, Samuel Ortiz wrote:
Hi Tomasz,
On Wed, Nov 03, 2010 at 05:23:44PM +0100, Tomasz Sterna wrote:
Samuel Ortiz sameo at linux.intel.com:
This interface connects fine when I manually run wpa_supplicant
for it.
But ConnMan fails to detect it as WiFi capable interface:
What's your
[I forgot to send this to meego-dev -- as this is developer related,
please post replies to meego-dev]
On Wed, Nov 3, 2010 at 11:26 AM, Niels Mayer wrote:
> A few weeks ago, Quim Gil posted a request to port Youtube-direct to
> some meego lists and IRC:
>> Qt Quick developer wanted to develop ope
Hi Tomasz,
On Wed, 2010-11-03 at 17:11 +0100, ext Tomasz Sterna wrote:
> On nie, 2010-10-31 at 18:51 +0100, Michał Sawicz wrote:
> > > It does not load a driver for my WiFi chip.
> >
> > What chip is that? Maybe it requires a firmware file? Does it work
> > when you load the module by hand?
>
>
Hi Stuart,
Am Mittwoch, 3. November 2010, 17:52:42 schrieb Stuart Hughes:
> Hi MeeGoers,
>
> Does anyone know how qemu detects the machine type when you mic-chroot
> to a (meego) root filesystem?
> When I mic-chroot into the meego-handset-armv7l-n900-1.1 on Ubuntu
> 10.10, uname -m incorrectly r
Hi,
I have Meego running on an OMAP4 board which does not have a touch
screen, I have an USB mouse connected to the board which works with X
and the meego desktop. But the cursor is not visible in Fennec browser.
Does Fennec work only with touch screen? If not how can I make it work
with the USB m
Hi Tomasz,
On Wed, Nov 03, 2010 at 05:23:44PM +0100, Tomasz Sterna wrote:
> Samuel Ortiz sameo at linux.intel.com:
> >> This interface connects fine when I manually run wpa_supplicant
> >> for it.
> >> But ConnMan fails to detect it as WiFi capable interface:
> > What's your ConnMan version ?
>
>
Hi MeeGoers,
Does anyone know how qemu detects the machine type when you mic-chroot
to a (meego) root filesystem?
When I mic-chroot into the meego-handset-armv7l-n900-1.1 on Ubuntu
10.10, uname -m incorrectly reports armv5tel
However on a Virtualbox / OpenSuse 11.2 installation, the same root
f
Samuel Ortiz sameo at linux.intel.com:
>> This interface connects fine when I manually run wpa_supplicant
>> for it.
>> But ConnMan fails to detect it as WiFi capable interface:
> What's your ConnMan version ?
Latest from trunk.
connman-0.62.2-1.2.armv7l.rpm
>> The module for WiFi interface was
On nie, 2010-10-31 at 18:51 +0100, Michał Sawicz wrote:
> > It does not load a driver for my WiFi chip.
>
> What chip is that? Maybe it requires a firmware file? Does it work
> when you load the module by hand?
BCM4325
It does require firmware, but i created proper /etc/modprobe.d/ pointing
to f
Hi,
Qt Mobility camera support prefers camerabin based implementation as backend so
that we do not need to have hardware specific implementation. Intel wanted to
contribute to the camera backend but the solution was implemented as a
customized pipeline using QGstreamerCaptureService to utilize
jari.paloja...@nokia.com wrote:
> 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
good point, they will surely differ. And I surely hope it stays on gst
level as you refer.
However, Meego tends to generalize packetizing as far as possible and
also gst-plugins packaging tend to gather stuff. So, I had a feeling the
camera stuff is not an exception.
If we consider...
qt-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
meego-architecture-boun...@lists.meego.com wrote:
> Hello,
>
> We encountered some matters with the recent MeeGo 1.1 Compliance
> Specification (draft 1.0.99.3) that would be nice to be clarified. Is
> there someone who could comment on these?
>
>
> 1) Specific definition of Platform API
>
> Li
Hi,
got no replies, from gang.a.hu ?
cc'd another contact I found working with mfldv4l2camsrc.
Thanks for the info Vivian. Enhancements sound fine, but doesn't it mean
that you have pushed a package that bases on enhancement branch into
Meego with a generic name and meaning ? From the name, I
Hello,
We encountered some matters with the recent MeeGo 1.1 Compliance
Specification (draft 1.0.99.3) that would be nice to be clarified. Is
there someone who could comment on these?
1) Specific definition of Platform API
Line 279:
"The Platform API consists of public interfaces from all libra
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
I would like to add that Qt Mobility roadmap can now be viewed in the Qt task
tracking system at http://bugreports.qt.nokia.com
http://bugreports.qt.nokia.com/browse/QTMOBILITY-633 - Bluetooth requirement.
To see all the roadmap items, click the label "mobility_roadmap" in the middle
of the pag
>>From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com]
>>On Behalf Of ext zhangwen363
>
>> Meego current bluetooth app which I found was one simple demo based on
>>bluez4 and do not find any bluetooth service framework but i found the
>>qt4.4 extended have a bluetooth service f
27 matches
Mail list logo
