Re: [MeeGo-dev] [QA-tools] g_ether module for all targets?

[sajeev.manikkoth]

Hi,

Is this functionality or any work around available to establish USB IP 
networking on MeeGo Aava device and the linux host?


Best Regards, 
Sajeev Manikkoth 
MeeGo SW R&D 
Phone: +918040159000 - Ext: 5338 
Hand Phone: +919663311378 

>-Original Message-
>From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On
>Behalf Of ext Timo Härkönen
>Sent: Friday, August 27, 2010 12:27 PM
>To: meego-dev@meego.com
>Subject: [MeeGo-dev] [QA-tools] g_ether module for all targets?
>
>Hi
>
>As far as I understand only kernel for N900 images has g_ether and allow
>IP connection through USB. Would it be possible to compile the module
>also for all the other targets also?
>
>Background for this is that we're looking for a generic way to do host
>based test execution on all reference devices. At least for me USB
>networking seems like the way to do it.
>
>Basically the setup is done so that there's private network between the
>host machine (192.168.2.14) and the device under test (192.168.2.15) and
>the tests are executed from the host over ssh using testrunner-lite.
>
>-Timo
>
>___
>MeeGo-dev mailing list
>MeeGo-dev@meego.com
>http://lists.meego.com/listinfo/meego-dev
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Buteo / data synchronization in MeeGo: hello world!

[Sateesh Kavuri]

On Tuesday 31 August 2010 09:49 PM, ext Luiz Augusto von Dentz wrote:

Hi,

On Tue, Aug 31, 2010 at 1:34 PM, Patrick Ohly  wrote:
   

On Mon, 2010-08-30 at 23:06 +0100, Luiz Augusto von Dentz wrote:
 

OpenSync there is a plugin in obexd to support synchronization over
obex, is there a plan to have such a plugin for buteo too?
   

There's a feature request open:
http://bugs.meego.com/show_bug.cgi?id=3868

It's a bit unclear to me if and when that'll get implemented.
 

Well, I can implement it, Im not sure why you guys are pointing to
meego bugs when meego is suppose to use what is upstream, that means
buteo and obexd upstream must agree on what is best to do here, or is
buteo suppose to be meego only?
   

Right now, Buteo is MeeGo only. Maybe after sometime it can be made
available in other repos.
   

The reason that Im asking this is because we did recently integrate
irmc (Sync) profile in obexd which we might use sync framework to get
the necessary information, so my hope is that we don't have to
duplicate code for handling obex connection when in fact we already
have a dedicated daemon doing that, obexd, in fact this should
simplify a lot the connection handling since all sync framework would
need to care is the syncml not obex and obviously obexd is already
doing connection handling for other obex targets.
   

What you describe is the design implemented in SyncEvolution and obexd
for Moblin. In the Buteo design, msyncd is the central daemon which
accepts incoming OBEX connections directly by calling libopenobex.
 

But it doesn't have to, actually msyncd already depend on obexd
anyway, since obexd handles other requests like capabilities request.
So my point is basically to use obexd (OBEX daemon) for what it is
for, handling OBEX connections, and leave msyncd to do the
synchronization, this should simplify the design.
   

Yes, obexd is used to serve capability files, but note that msyncd does not
have a direct dependency on obexd and it is also not required for some 
of the

usecases, like online sync. Otherwise the syncml plugin uses libopenobex to
 handle the communication with the peers. msyncd could depend on obexd,
 but for that a separate plug-in has to be written that could pass on the
 syncml messages between obexd and msyncd, which in my view is not a good
 dependency. Also note that msyncd handles many other kinds of 
protocols other

than syncml (MTP, for example).

Regards,

   

--
Sateesh
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] [MeeGo-Dev][PATCH] Topcliff: Update PCH_I2C driver to 2.6.35

[Masayuki Ohtake]

Hi, Greg

Sorry for late response.

Thanks, Ohtake(OKISemi)
- Original Message - 
From: "Greg KH" 
To: "Masayuki Ohtak" 
Cc: ; "Wang Yong Y" ; "Wang Qi" 
; "Andrew"
; ; 
; 
Sent: Friday, August 06, 2010 11:24 PM
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_I2C driver to 2.6.35


> On Fri, Aug 06, 2010 at 01:33:24PM +0900, Masayuki Ohtak wrote:
> > I2C driver of Topcliff PCH
> >
> > Topcliff PCH is the platform controller hub that is going to be used in
> > Intel's upcoming general embedded platform. All IO peripherals in
> > Topcliff PCH are actually devices sitting on AMBA bus.
> > Topcliff PCH has I2C I/F. Using this I/F, it is able to access system
> > devices connected to I2C.
> >
> > Signed-off-by: Masayuki Ohtake 
>
>
> Why not run this by the i2c maintainer and developers as well?

I will add i2c maintainer and developers next submission.

>
> You do know about the scripts/get_maintainer.pl program to tell you who
> to copy when sending a patch, right?  Please use that.
>
> >
> > ---
> >  drivers/i2c/busses/Kconfig   |8 +
> >  drivers/i2c/busses/Makefile  |3 +
> >  drivers/i2c/busses/i2c-pch.c |  910 
> > ++
> >  drivers/i2c/busses/i2c-pch.h |  147 +++
> >  drivers/i2c/i2c-dev.c|   21 +
> >  5 files changed, 1089 insertions(+), 0 deletions(-)
> >  create mode 100644 drivers/i2c/busses/i2c-pch.c
> >  create mode 100644 drivers/i2c/busses/i2c-pch.h
> >
> > diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> > index 5f318ce..98e7201 100644
> > --- a/drivers/i2c/busses/Kconfig
> > +++ b/drivers/i2c/busses/Kconfig
> > @@ -7,6 +7,14 @@ menu "I2C Hardware Bus support"
> >  comment "PC SMBus host controller drivers"
> >  depends on PCI
> >
> > +config PCH_I2C
> > + tristate "PCH I2C"
> > + depends on PCI
> > + help
> > +   This driver is for PCH I2C of Topcliff which is an IOH for x86
> > +   embedded processor.
> > +   This driver can access PCH I2C bus device.
> > +
> >  config I2C_ALI1535
> >  tristate "ALI 1535"
> >  depends on PCI
> > diff --git a/drivers/i2c/busses/Makefile b/drivers/i2c/busses/Makefile
> > index 302c551..3e6b8d6 100644
> > --- a/drivers/i2c/busses/Makefile
> > +++ b/drivers/i2c/busses/Makefile
> > @@ -75,3 +75,6 @@ obj-$(CONFIG_SCx200_I2C) += scx200_i2c.o
> >  ifeq ($(CONFIG_I2C_DEBUG_BUS),y)
> >  EXTRA_CFLAGS += -DDEBUG
> >  endif
> > +
> > +obj-$(CONFIG_PCH_I2C) += pch_i2c.o
> > +pch_i2c-objs := i2c-pch.o
>
> Why not just name your file i2c-pci.c and then you don't need this
> two-step Makefile mess?
>
> > diff --git a/drivers/i2c/busses/i2c-pch.c b/drivers/i2c/busses/i2c-pch.c
> > new file mode 100644
> > index 000..7939781
> > --- /dev/null
> > +++ b/drivers/i2c/busses/i2c-pch.c
> > @@ -0,0 +1,910 @@
> > +/*
> > + * Copyright (C) 2010 OKI SEMICONDUCTOR Co., LTD.
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License as published by
> > + * the Free Software Foundation; version 2 of the License.
> > + *
> > + * This program is distributed in the hope that it will be useful,
> > + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> > + * GNU General Public License for more details.
> > + *
> > + * You should have received a copy of the GNU General Public License
> > + * along with this program; if not, write to the Free Software
> > + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307, 
> > USA.
> > + */
> > +
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +#include 
> > +
> > +#include "i2c-pch.h"
>
> Why do you need a .h file for this driver?

I will delete.

>
> 
>
> > diff --git a/drivers/i2c/i2c-dev.c b/drivers/i2c/i2c-dev.c
> > index f4110aa..53e13de 100644
> > --- a/drivers/i2c/i2c-dev.c
> > +++ b/drivers/i2c/i2c-dev.c
> > @@ -36,6 +36,7 @@
> >  #include 
> >  #include 
> >  #include 
> > +#include "busses/i2c-pch.h"
>
> Note how no other i2c driver needs to be included here...

I will delete.

>
> >  static struct i2c_driver i2cdev_driver;
> >
> > @@ -372,6 +373,12 @@ static long i2cdev_ioctl(struct file *file, unsigned 
> > int cmd, unsigned long arg)
> >  struct i2c_client *client = file->private_data;
> >  unsigned long funcs;
> >
> > + unsigned long pch_mode;
> > + int ret;
> > +
> > + struct i2c_msg msg;
> > + unsigned char msgbuf[1];
> > +
> >  dev_dbg(&client->adapter->dev, "ioctl, cmd=0x%02x, arg=0x%02lx\n",
> >  cmd, arg);
> >
> > @@ -427,6 +434,20 @@ static long i2cdev_ioctl(struct file *file, unsigned 
> > int cmd, unsigned long arg)
> >  */
> >  client->adapter->timeout = msecs_to_jiffies(arg * 10);
> >  break;
> > + case I2C_MODE_SEL:
> > + pch_mode = arg;
> > +
> > + if (pch_mode <= 4) {
> > + msgbuf[0] = pch_mode;
> > + 

Re: [MeeGo-dev] [MeeGo-Dev][PATCH] Topcliff: Update PCH_I2C driver to 2.6.35

[Masayuki Ohtake]

Hi Arjan,

Sorry, for late response.
- Original Message - 
From: "Arjan van de Ven" 
To: "Masayuki Ohtak" 
Cc: ; ; ; 
;
; ; 
Sent: Friday, August 06, 2010 1:40 PM
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_I2C driver to 2.6.35


> On 8/5/2010 9:33 PM, Masayuki Ohtak wrote:
> >
> > +config PCH_I2C
> > + tristate "PCH I2C"
> >
>
> this is really not very descriptive. Can you make it "OKI Semi PCH I2C
> controller" or something

We will modify.

>
> if you has human get asked "PCH I2C"... almost nobody will know what
> that means.+static irqreturn_t pch_handler_ch0(int irq, void *pData);
>
>
> > +static irqreturn_t(*pch_handler_list[PCH_MAX_CHN]) (int irq, void *pData) 
> > = {
> > + pch_handler_ch0,
> > +};
> >
>
> humm what is this for??

This is callback function list for mulit-cahnnel I2C device.

>
>
> > +
> > +static inline void pch_setbit(void __iomem *addr, u32 offset, u32 bitmask)
> > +{
> > + iowrite32(((ioread32(addr + offset)) | (bitmask)), (addr + offset));
> > +}
> >
>
> this might be more readble if it's made 3 lines with a local variable...
> + "Cleared the registers PCH_I2CCTL,PCH_I2CMOD,PCH_I2CBUFFOR\n,"
>
>
> > + "PCH_I2CBUFSLV,PCH_I2CBUFSUB,PCH_I2CBUFMSK,\n"
> >

I will divide to 3 lines.

>
> what's that weird character ?diff --git a/drivers/i2c/i2c-dev.c
> b/drivers/i2c/i2c-dev.c
> + case I2C_MODE_SEL:
>
>
> > + pch_mode = arg;
> > +
> > + if (pch_mode <= 4) {
> > + msgbuf[0] = pch_mode;
> > + msg.buf = msgbuf;
> > + msg.len = 1;
> > + msg.flags = 0;
> > + ret = i2c_transfer(client->adapter, &msg, 1);
> >
>
> in generic code??
>
>

I will revert i2c-dev.c.


I will submit modified patch soon.

Thanks, Ohtake(OKISemi)


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] [PATCH 0/4] cy8ctmg110 touch screen improvements

[Gary Birkett]

James,

that is great to know, thanks for clarifications on both parts!
I did not see the details of the driver body itself in the patch hence
questions :)

As for a kalman filter, the equation itself looks heavy [1] and would
understandably have to be recalculated every frame unless an incremental
variation can be created.
The version I did initially with just taking fractions of each sample was
easily achieved [2] and lightweight enough to be useful without consuming
battery.
I bet for the use I did it wouldn't make much difference, but in scientific
situations it would be good to try.

Regards,

Gary


[1] C implementation
http://www.its.washington.edu/software/kalman_fil.html

[2] Maemo wiki with Accelerometer smoothing
http://wiki.maemo.org/Accelerometers#Smoothed_C_interface


On Tue, Aug 31, 2010 at 5:23 PM, James  wrote:

> On 08/31/2010 05:34 AM, Gary Birkett wrote:
>
>> James,
>>
>> A question about the patch for capacitive
>>
>> " cy8ctmg110: Added fuzz to ABS_X and ABS_Y to remove jitter"
>>
>> I cannot determine from the patch what it does, does it reduce the
>> resolution down to 4 unit blocks, or does it still allow single unit
>> sensitivity whilst removing jitters from around it?
>>
> You can see drivers/input/input.c input_defuzz_abs_event() for
> implementation details on how fuzz is used internally within the input
> system.
>
> The result is that jitter around a stable point is reduced; the device
> still retains the same total sensitivity, but once a contact point is made,
> the data has a tendency to stick to that value until the threshold is
> crossed.
>
>
>> If it it indeed the resolution limiting, perhaps something I did in the
>> past to remove jitter from the very noisy accelerometer might be another
>> alternative.
>>
>> At each new reading from the sensor, I would move the "cursor" a
>> percentage fraction closer to that point rather than directly using it.
>>
> A kalman filter (or similar predictive algorithm) is also a great way to
> remove noise from an accelerometer, without introducing latency into the
> sensor read path.
>
> James
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Buteo / data synchronization in MeeGo: hello world!

[Patrick Ohly]

On Tue, 2010-08-31 at 17:19 +0100, Luiz Augusto von Dentz wrote:
> Hi,
> 
> On Tue, Aug 31, 2010 at 1:34 PM, Patrick Ohly  wrote:
> > On Mon, 2010-08-30 at 23:06 +0100, Luiz Augusto von Dentz wrote:
> >> OpenSync there is a plugin in obexd to support synchronization over
> >> obex, is there a plan to have such a plugin for buteo too?
> >
> > There's a feature request open:
> > http://bugs.meego.com/show_bug.cgi?id=3868
> >
> > It's a bit unclear to me if and when that'll get implemented.
> 
> Well, I can implement it, Im not sure why you guys are pointing to
> meego bugs when meego is suppose to use what is upstream,

*If* an upstream project is used, *then* the policy is to work upstream.
But there's no policy that all code in MeeGo has to be released and
maintained as a separate upstream project. Many core components were
specifically developed for Harmattan and MeeGo.

>  that means
> buteo and obexd upstream must agree on what is best to do here, or is
> buteo suppose to be meego only?

Note that I am only commenting here from the view point of
an outside observer of the Buteo project, not as one of its developers
(which I am not).

At the moment, Buteo is getting developed inside Nokia: all the
developers are from Nokia, code gets committed to Nokia-internal repos,
the change log contains only references to a closed issue tracker that
(presumably) covers the next Nokia product.

Code gets copied to the MeeGo repos occasionally. The only public issue
tracker is the one in bugs.meego.com, but it doesn't see much activity.
Both will probably change at some point in the future, but we are not
there yet.

Beyond MeeGo, everything is speculation at this point. I have no idea
whether the developers are interested in supporting additional
platforms, and have the necessary time. The PIM storages that Buteo
interfaces with have to implement a lot more functionality than is
commonly found in PIM storage systems. Porting to Evolution Data Server
or Akonadi (to name just two that I am familiar with) will be hard.

> >> The reason that Im asking this is because we did recently integrate
> >> irmc (Sync) profile in obexd which we might use sync framework to get
> >> the necessary information, so my hope is that we don't have to
> >> duplicate code for handling obex connection when in fact we already
> >> have a dedicated daemon doing that, obexd, in fact this should
> >> simplify a lot the connection handling since all sync framework would
> >> need to care is the syncml not obex and obviously obexd is already
> >> doing connection handling for other obex targets.
> >
> > What you describe is the design implemented in SyncEvolution and obexd
> > for Moblin. In the Buteo design, msyncd is the central daemon which
> > accepts incoming OBEX connections directly by calling libopenobex.
> 
> But it doesn't have to, actually msyncd already depend on obexd
> anyway, since obexd handles other requests like capabilities request.
> So my point is basically to use obexd (OBEX daemon) for what it is
> for, handling OBEX connections, and leave msyncd to do the
> synchronization, this should simplify the design.

For what it's worth, I agree with you. After all, I came to the same
conclusion before ;-)

Coming back to a more technical discussion: there are pros and cons for
both approaches. obexd: code reuse, clean separation. msyncd: all
communication local.

You could use obexd to handle OBEX, then talk to some msyncd server
plugin over some custom (D-Bus) protocol to handle the SyncML messages
and syncing itself. There's example code on the obexd side with the
"syncevolution" plugin. You could even reimplement the server-side D-Bus
API and thus make Buteo work without having to touch obexd at all. See
http://api.syncevolution.org/#Server.Connect
http://api.syncevolution.org/#Connection

There are no example server plugins for Buteo, so you'll have to ask
Sateesh if you cannot figure out how to write one from the design
document and the comments in buteo-syncfs/msyncd.

-- 
Best Regards

Patrick Ohly
Senior Software Engineer

Intel GmbH
Open Source Technology Center   
Pützstr. 5  Phone: +49-228-2493652
53129 Bonn
Germany

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] [QA-tools] Meeting

[ville.p.ilvonen]

Here goes minutes - 
http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-31-11.57.html
More info - http://wiki.meego.com/Quality/QA-tools

Thanks and hope to see you/your input,

-Ville

From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] On Behalf Of 
Ilvonen Ville.P (Nokia-MS/Tampere)
Sent: Friday, August 27, 2010 11:03 AM
To: meego-dev@meego.com
Subject: [MeeGo-dev] [QA-tools] Meeting

Hi,

We'll have the first meeting regarding QA tools work next Tuesday, August 31 
12:00 UTC.
I listed it at MeeGo meeting schedules [1] and agenda is also available [2].

More info on Quality Assurance Tools activities available at 
http://wiki.meego.com/Quality

Regards,

Ville
MeeGo QA tools lead (act.)

[1] http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule#August_Schedule
[2] http://wiki.meego.com/Quality/QA-tools#Meetings
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] [PATCH 0/4] cy8ctmg110 touch screen improvements

[James]

On 08/31/2010 05:34 AM, Gary Birkett wrote:

James,

A question about the patch for capacitive

" cy8ctmg110: Added fuzz to ABS_X and ABS_Y to remove jitter"

I cannot determine from the patch what it does, does it reduce the 
resolution down to 4 unit blocks, or does it still allow single unit 
sensitivity whilst removing jitters from around it?
You can see drivers/input/input.c input_defuzz_abs_event() for 
implementation details on how fuzz is used internally within the input 
system.


The result is that jitter around a stable point is reduced; the device 
still retains the same total sensitivity, but once a contact point is 
made, the data has a tendency to stick to that value until the threshold 
is crossed.


If it it indeed the resolution limiting, perhaps something I did in 
the past to remove jitter from the very noisy accelerometer might be 
another alternative.


At each new reading from the sensor, I would move the "cursor" a 
percentage fraction closer to that point rather than directly using it.
A kalman filter (or similar predictive algorithm) is also a great way to 
remove noise from an accelerometer, without introducing latency into the 
sensor read path.


James

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] MRemoteThemeDaemon: Failed to connect to theme daemon (IPC)

[Poussa Sakari]

On 08/20/10 17:07, ext Asvindh Kumar R wrote:

Hi,
I am new to meego and trying meego-touch
i have installed MeeGo Touch on ubuntu 10.4 + qt 4.7 beta 2  ( is the 
the correct version of Qt i am using ??)
followed the steps from here 
http://apidocs.meego.com/mtf/installation.html


After building the 
*...@ubuntu:~/meego/meegotouch-theme/libmeegotouch/* , i am trying to 
execute helloworld program but i get this error

MRemoteThemeDaemon: Failed to connect to theme daemon (IPC)
MThemeDaemon - base theme directory not found: 
/home/akr/meego/meegotouch-theme/libmeegotouch/install/share/themes/base/meegotouch/libmeegotouchcore/style. 
Please (re)install meegotouchtheme package.

Aborted

Any pointers on this error... or should i be installing meego-touch 
libs inside meego-sdk ?


Have you build and run the mthemedaemon from libmeegotouch directory:

cd mthemedaemon
qmake
make
./mthemedaemon

-sakari



Thanks & Regards
Asvindh R


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego BootLoader

[anoop ravi]

meego uses syslinux.
located at
/boot/extlinux/extlinux.conf ---have a look at this!!
*
*
On Mon, Aug 30, 2010 at 5:10 PM, Hari  wrote:

>
> Hi One and All.
>
> Plz let me know the default boot loader in meego.
>
>
> Regards
> Hari
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Buteo / data synchronization in MeeGo: hello world!

[Luiz Augusto von Dentz]

Hi,

On Tue, Aug 31, 2010 at 1:34 PM, Patrick Ohly  wrote:
> On Mon, 2010-08-30 at 23:06 +0100, Luiz Augusto von Dentz wrote:
>> OpenSync there is a plugin in obexd to support synchronization over
>> obex, is there a plan to have such a plugin for buteo too?
>
> There's a feature request open:
> http://bugs.meego.com/show_bug.cgi?id=3868
>
> It's a bit unclear to me if and when that'll get implemented.

Well, I can implement it, Im not sure why you guys are pointing to
meego bugs when meego is suppose to use what is upstream, that means
buteo and obexd upstream must agree on what is best to do here, or is
buteo suppose to be meego only?

>> The reason that Im asking this is because we did recently integrate
>> irmc (Sync) profile in obexd which we might use sync framework to get
>> the necessary information, so my hope is that we don't have to
>> duplicate code for handling obex connection when in fact we already
>> have a dedicated daemon doing that, obexd, in fact this should
>> simplify a lot the connection handling since all sync framework would
>> need to care is the syncml not obex and obviously obexd is already
>> doing connection handling for other obex targets.
>
> What you describe is the design implemented in SyncEvolution and obexd
> for Moblin. In the Buteo design, msyncd is the central daemon which
> accepts incoming OBEX connections directly by calling libopenobex.

But it doesn't have to, actually msyncd already depend on obexd
anyway, since obexd handles other requests like capabilities request.
So my point is basically to use obexd (OBEX daemon) for what it is
for, handling OBEX connections, and leave msyncd to do the
synchronization, this should simplify the design.

Regards,

-- 
Luiz Augusto von Dentz
Computer Engineer
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] lsmod output

[Arjan van de Ven]

On 8/31/2010 7:30 AM, Thiago Macieira wrote:

Em Terça-feira 31 Agosto 2010, às 16:12:28, Hari escreveu:
   

The command lsmod which prints the contents of the
/proc/modules  file.
It shows which loadable kernel
modules  are
currently loaded. but in meego I tried this command and I am not getting a
  desired output. I tried this command in fedora it shows all loaded modules
in the system
 

What is your desired output and why do you think the output you are getting is
in any way wrong?

   




and why is this question appropriate for meego-dev ? it clearly isn't 
about the development of meego


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] git fail when i try to clone libmeegotouch

[Dave Neary]

Hi,

Dave Neary wrote:
> I just tried this, and it works for me. Try removing the directory &
> trying again. Perhaps someone rebased the repository you're pulling
> from, and you have an older clone with some commits that don't exist any
> more?

Correction: it failed, in the same way, right at the end. After a lot of
other messages. Using the git:// URL worked.

-- 
maemo.org docsmaster
Email: dne...@maemo.org
Jabber: bo...@jabber.org

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] lsmod output

[Thiago Macieira]

Em Terça-feira 31 Agosto 2010, às 16:12:28, Hari escreveu:
> The command lsmod which prints the contents of the
> /proc/modules file.
> It shows which loadable kernel
> modules are
> currently loaded. but in meego I tried this command and I am not getting a
>  desired output. I tried this command in fedora it shows all loaded modules
> in the system

What is your desired output and why do you think the output you are getting is 
in any way wrong?

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
  PGP/GPG: 0x6EF45358; fingerprint:
  E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358


signature.asc
Description: This is a digitally signed message part.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] lsmod output

[Ameya Palande]

On Tue, 2010-08-31 at 16:12 +0200, ext Hari wrote:
> The command lsmod which prints the contents of the /proc/modules file.
> It shows which loadable kernel modules are currently loaded. but in
> meego I tried this command and I am not getting a  desired output. I
> tried this command in fedora it shows all loaded modules in the
> system 
> 
> 
> May I know why it is like that , 

Again (same like bootloader case) which meego are you talking about?

For meego handset release on Nokia N900 I got following output:

[r...@localhost ~]# lsmod
Module  Size  Used by
sco 8310  2 
bnep9739  2 
l2cap  36904  3 bnep
crc16   1289  1 l2cap
bluetooth  56319  5 sco,bnep,l2cap
smc91x 20531  0 
mii 4104  1 smc91x
cmt_speech 12407  0 
wl1251_spi  3139  0 
wl1251 72734  1 wl1251_spi
ssi_protocol   11869  1 cmt_speech
hsi_char   10472  0 
cmt 2517  1 ssi_protocol
mac80211  163170  2 wl1251_spi,wl1251
omap_ssi   13185  1 ssi_protocol
cfg80211  143100  2 wl1251,mac80211
crc71051  1 wl1251_spi
omaplfb 7162  1 
pvrsrvkm  132999  4 omaplfb
g_ether33479  0 
isp1704_charger 3268  0 
power_supply8965  1 isp1704_charger
tsl2563 5537  0 
lis3lv02d_i2c   2139  0 
leds_lp552310317  0 
lis3lv02d   9883  1 lis3lv02d_i2c
input_polldev   3864  1 lis3lv02d
industrialio9865  2 tsl2563
rtc_twl 4712  0 
led_class   2836  1 leds_lp5523
twl4030_pwrbutton   1501  0 
gpio_keys   5773  0 

Cheers,
Ameya.

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] lsmod output

[Hari]

The command lsmod which prints the contents of the
/proc/modules file.
It shows which loadable kernel
modules are
currently loaded. but in meego I tried this command and I am not getting a
 desired output. I tried this command in fedora it shows all loaded modules
in the system

May I know why it is like that ,


Best Regards
Hari
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego Image creating problem

[ext-jahnavi.boppana]

Hi,

What error do you get?

- jahnavi

From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] On Behalf Of 
ext Hari [haripra...@gmail.com]
Sent: Tuesday, August 31, 2010 3:10 PM
To: Development for the MeeGo Project (discussion list)
Subject: [MeeGo-dev] Meego Image creating problem

Hi one and all,☺

I have tried to make an os image of Meego for  Netbooks .  reference link  
 
http://wiki.meego.com/Image_Creation_For_Beginners

steps what I have done

Step 1

Installed mic2 and related packages from meego repo .

Step 2

downloaded the kickstart file from the the website and copied to /home/meego


http://repo.meego.com/MeeGo/builds/trunk/0.9.80.1.20100330.1/core/images/meego-preview-netbook-core/meego-preview-netbook-core.ks


edited the downloaded kick start these fields  @Core and @Base to Meego Core 
and Meego Base respectively


STEP 3 - Create MeeGo Livecd Image
MIC has to be run with root privileges using 'sudo'.
Here is the command to create a MeeGo livecd image which I got from the wiki
sudo mic-image-creator 
--config=/home/meego/meego-preview-netbook-core.ks
  --format=livecd --cache=mycache


I got a Meego os. ISO file and I have extracted the ISO file and write in to a 
DVD using ImageBurn software.
But the the Image is not working properly while installing os to hdd and boot 
from livecd. Getting error
☺
May I missing anything while doing Image creation?☺


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] [PATCH 0/4] cy8ctmg110 touch screen improvements

[Gary Birkett]

James,

A question about the patch for capacitive

" cy8ctmg110: Added fuzz to ABS_X and ABS_Y to remove jitter"

I cannot determine from the patch what it does, does it reduce the
resolution down to 4 unit blocks, or does it still allow single unit
sensitivity whilst removing jitters from around it?

If it it indeed the resolution limiting, perhaps something I did in the past
to remove jitter from the very noisy accelerometer might be another
alternative.

At each new reading from the sensor, I would move the "cursor" a percentage
fraction closer to that point rather than directly using it.
In a jittery noisy environment this allows it to retain accuracy whilst
removing the jitter.

Just thoughts based on this patch and not knowing how it works inside the
black box controller.
If it already does this then that is great!


Gary



On Thu, Aug 19, 2010 at 11:21 PM, James  wrote:

> This series fixes two bugs (jitter and calibration), provides some
> general cleanups, and adds multi-touch capabilities to for the
> cy8ctmg110 touch screen driver.
>
> James Ketrenos (4):
>  cy8ctmg110: Removed X and Y scaling factor for send_event
>  cy8ctmg110: Rework to be multi-touch ready
>  cy8ctmg110: Added fuzz to ABS_X and ABS_Y to remove jitter
>
>  cy8ctmg110: Add multi-touch capabilities
>
>  drivers/input/touchscreen/Kconfig |   13 ++
>  drivers/input/touchscreen/cy8ctmg110_ts.c |  179
> +
>  2 files changed, 142 insertions(+), 50 deletions(-)
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego BootLoader

[Hari]

On Tue, Aug 31, 2010 at 5:46 PM, Hari  wrote:

>
>
> On Tue, Aug 31, 2010 at 5:29 PM, Poussa Sakari wrote:
>
>> On 08/30/10 14:57, ext Thiago Macieira wrote:
>>
>>> Em Segunda-feira 30 Agosto 2010, às 13:40:47, Hari escreveu:
>>>
>>>
 Hi One and All.

 Plz let me know the default boot loader in meego.


>>> extlinux
>>>
>>>
>>>
>> No, there is no such thing (default meego bootloader). As Ameya said, it
>> is platform specific.
>>
>> -sakari
>>
>>
>> __ _
>> MeeGo-dev mailing list
>> MeeGo-dev@meego.com
>> http://lists.meego.com/listinfo/meego-dev
>>
>
>
>
>
> Hi  to conclude
>
>
>
>
> The default bootloader in Meego Netbook and Nettop is “ extlinux  - it is a
> derivative of new syslinux
>
> Boot loader is very much hardware dependant so that each platform boot
> loader differs , like
>
> Netbook and Nettop uses  - extlinux
>
> N900 uses nolo
>
> *Aava* Mobile Intel *Moorestown* platform images uses kboot
>
>
>
> No idea what another platform os images uses ? J
>
>
>
> Best Regards
>
> Hari
>


Hi one and all , thanks for the help !
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Meego Image creating problem

[Hari]

Hi one and all,J



I have tried to make an os image of Meego for  Netbooks .  reference
link  
http://wiki.meego.com/Image_Creation_For_Beginners



*steps what I have done*



*Step 1*



Installed mic2 and related packages from meego repo .



*Step 2*



downloaded the kickstart file from the the website and copied to *
/home/meego*


 

http://repo.meego.com/MeeGo/builds/trunk/0.9.80.1.20100330.1/core/images/meego-preview-netbook-core/meego-preview-netbook-core.ks





edited the downloaded kick start these fields  @Core and @Base to Meego Core
and Meego Base respectively



 *STEP 3 - Create MeeGo Livecd Image*

MIC has to be run with root privileges using 'sudo'.

Here is the command to create a MeeGo livecd image which I got from the wiki

sudo mic-image-creator
--config=/home/meego/meego-preview-netbook-core.ks
  --format=livecd --cache=mycache





I got a Meego os. ISO file and I have extracted the ISO file and write in to
a DVD using ImageBurn software.

But the the Image is not working properly while installing os to hdd and
boot from livecd. Getting error

J

May I missing anything while doing Image creation?J
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Meego BootLoader

[Poussa Sakari]

On 08/30/10 14:57, ext Thiago Macieira wrote:

Em Segunda-feira 30 Agosto 2010, às 13:40:47, Hari escreveu:
   

Hi One and All.

Plz let me know the default boot loader in meego.
 

extlinux

   
No, there is no such thing (default meego bootloader). As Ameya said, it 
is platform specific.


-sakari

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Buteo / data synchronization in MeeGo: hello world!

[Patrick Ohly]

On Mon, 2010-08-30 at 23:06 +0100, Luiz Augusto von Dentz wrote:
> OpenSync there is a plugin in obexd to support synchronization over
> obex, is there a plan to have such a plugin for buteo too?

There's a feature request open:
http://bugs.meego.com/show_bug.cgi?id=3868

It's a bit unclear to me if and when that'll get implemented.

> The reason that Im asking this is because we did recently integrate
> irmc (Sync) profile in obexd which we might use sync framework to get
> the necessary information, so my hope is that we don't have to
> duplicate code for handling obex connection when in fact we already
> have a dedicated daemon doing that, obexd, in fact this should
> simplify a lot the connection handling since all sync framework would
> need to care is the syncml not obex and obviously obexd is already
> doing connection handling for other obex targets.

What you describe is the design implemented in SyncEvolution and obexd
for Moblin. In the Buteo design, msyncd is the central daemon which
accepts incoming OBEX connections directly by calling libopenobex.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] git fail when i try to clone libmeegotouch

[Dave Neary]

Hi,

Tom Chen wrote:
> i want git clone libmeegotouch from gitorious.org
> , but i always got the fail. the output as below:

I just tried this, and it works for me. Try removing the directory &
trying again. Perhaps someone rebased the repository you're pulling
from, and you have an older clone with some commits that don't exist any
more?

Cheers,
Dave.

-- 
maemo.org docsmaster
Email: dne...@maemo.org
Jabber: bo...@jabber.org

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] git fail when i try to clone libmeegotouch

[Ville M. Vainio]

On Tue, Aug 31, 2010 at 12:28 PM, Tom Chen  wrote:
> Hi,
>     i want git clone libmeegotouch from gitorious.org, but i always got the
> fail. the output as below:
> [...@tom MeeGo-Touch-Framework]$ git clone
> http://git.gitorious.org/meegotouch/libmeegotouch.git

How about

git clone git://gitorious.org/meegotouch/libmeegotouch.git

> Initialized empty Git repository in
> /home/tom/Meego/MeeGo-Touch-Framework/libmeegotouch/.git/
> error: Unable to get pack file
> http://git.gitorious.org/meegotouch/libmeegotouch.git/objects/pack/pack-6e15a4543ae52a98d7dc9f22fea615f2760e8904.pack
> transfer closed with 20447929 bytes remaining to read
> error: Unable to find e0e4b328941ad09b1f2d768f1f0702ea24135de5 under
> http://git.gitorious.org/meegotouch/libmeegotouch.git
> Cannot obtain needed object e0e4b328941ad09b1f2d768f1f0702ea24135de5
> while processing commit 60589ff89b0f7042382689db78021fd5ae86451d.
> error: Fetch failed.
> [...@tom MeeGo-Touch-Framework]$
> Could someone help me for this issue? thanks.
> Br
> Tom Chen
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>
>



-- 
Ville M. Vainio @@ Forum Nokia
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] git fail when i try to clone libmeegotouch

[Tom Chen]

Hi,

i want git clone libmeegotouch from gitorious.org, but i always got the
fail. the output as below:

[...@tom MeeGo-Touch-Framework]$ git clone
http://git.gitorious.org/meegotouch/libmeegotouch.git
Initialized empty Git repository in
/home/tom/Meego/MeeGo-Touch-Framework/libmeegotouch/.git/
error: Unable to get pack file
http://git.gitorious.org/meegotouch/libmeegotouch.git/objects/pack/pack-6e15a4543ae52a98d7dc9f22fea615f2760e8904.pack
transfer closed with 20447929 bytes remaining to read
error: Unable to find e0e4b328941ad09b1f2d768f1f0702ea24135de5 under
http://git.gitorious.org/meegotouch/libmeegotouch.git
Cannot obtain needed object e0e4b328941ad09b1f2d768f1f0702ea24135de5
while processing commit 60589ff89b0f7042382689db78021fd5ae86451d.
error: Fetch failed.
[...@tom MeeGo-Touch-Framework]$

Could someone help me for this issue? thanks.

Br
Tom Chen
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] meego codec support

[Gray, Mark D]

Thanks for you help!

Mark

-Original Message-
From: bren...@fridu.net [mailto:bren...@fridu.net] On Behalf Of Brendan Le Foll
Sent: 27 August 2010 20:48
To: Gray, Mark D
Cc: meego-dev@meego.com
Subject: Re: [MeeGo-dev] meego codec support

Look up the good, ugly and bad plugin sets from gstreamers. The
differences are explained here -
http://en.wikipedia.org/wiki/GStreamer

There are other plugins like the broadcom one that are not in the
plugin packs and others that you need a license for like the Fluendo
codecs.

Enjoy!

On another note, I should really learn to stop pressing reply...

On 27 August 2010 16:28, Gray, Mark D  wrote:
> Hi,
>
> Thanks for your informative answer! Is there a list of available GStreamer 
> codecs anywhere?
>
> Mark
>
> -Original Message-
> From: bren...@fridu.net [mailto:bren...@fridu.net] On Behalf Of Brendan Le 
> Foll
> Sent: 27 August 2010 14:35
> To: Gray, Mark D
> Subject: Re: [MeeGo-dev] meego codec support
>
> Hello,
>
> Meego uses the gstreamer architecture. You can read a little about it
> here : http://meego.com/developers/meego-architecture/media-services.
> I recommend you read up about it but basically it's a plugins
> architecture and plugins exist for lots of different media and
> hardware.
>
> For hardware accelerated gstreamer plugins see this for the
> sodaville/canmore SOC plaforms -
> https://core.fluendo.com/gstreamer/trac/browser/trunk/gst-fluendo-ismd
>
> There is also a FOSS gstreamer plugin for the broadcom CrystalHD
> 70010/70012 + 70015 accelerator cards. Also Fluendo have a proprietary
> plugin that uses libva to provide hardware acceleration on platforms
> supporting it (US15W/poulsbo for example with EMGD driver).
>
> Hope that helps!
>
> Brendan
>
> On 27 August 2010 14:17, Gray, Mark D  wrote:
>> Hi all,
>>
>>
>>
>> I am trying to find out information regarding the supported video, audio and
>> voice codecs in the MeeGo stack.
>>
>>
>>
>> What are the codecs that will be available as software-only implementations?
>> Is there any work been carried out on acceleration of these codecs on
>> specific platforms?
>>
>>
>>
>> If anyone can answer this or point me in the right direction, I would be
>> very grateful! J
>>
>>
>>
>> Regards,
>>
>>
>>
>> Mark
>>
>>
>>
>>
>>
>>
>>
>> _
>>
>>
>>
>> Mark Gray
>>
>> Software Engineer
>>
>> EI-DSP Team
>>
>>
>>
>> Intel Shannon
>>
>> Dromore House
>>
>> Shannon East Industrial Estate
>>
>> County Clare
>>
>> Ireland
>>
>>
>>
>> Tel: +353 (61) 47 7748
>>
>> INET: 8 247 7748
>>
>>
>>
>>
>>
>> --
>> Intel Shannon Limited
>> Registered in Ireland
>> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
>> Registered Number: 308263
>> Business address: Dromore House, East Park, Shannon, Co. Clare
>>
>> This e-mail and any attachments may contain confidential material for the
>> sole use of the intended recipient(s). Any review or distribution by others
>> is strictly prohibited. If you are not the intended recipient, please
>> contact the sender and delete all copies.
>>
>>
>> ___
>> MeeGo-dev mailing list
>> MeeGo-dev@meego.com
>> http://lists.meego.com/listinfo/meego-dev
>>
>>
> --
> Intel Shannon Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
> Business address: Dromore House, East Park, Shannon, Co. Clare
>
> This e-mail and any attachments may contain confidential material for the 
> sole use of the intended recipient(s). Any review or distribution by others 
> is strictly prohibited. If you are not the intended recipient, please contact 
> the sender and delete all copies.
>
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>
--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] where to get the latest kickstart (.ks) file

[fathi.boudra]

http://meego.gitorious.org/meego-os-base/image-configurations

From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of ext adam.mik...@tieto.com
Sent: 31 August, 2010 10:30
To: zhg...@gmail.com; meego-dev@meego.com
Subject: Re: [MeeGo-dev] where to get the latest kickstart (.ks) file

Try: http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages

Best regards,
Adam


From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of gw zhang
Sent: Wednesday, August 25, 2010 10:34 AM
To: meego-dev@meego.com
Subject: [MeeGo-dev] where to get the latest kickstart (.ks) file
Hi All,
I don't know where to post this question, I hope I post it in the right 
place.

I follow this link 
http://wiki.meego.com/ARM/Creating_ARM_image_using_MeeGo_Image_Creator#Get_and_install_MeeGo_Image_Creator_code
 to run image creator, but after I download kickstart from 
http://repo.meego.com/MeeGo/devel/n900/images/,  The repo url 
(http://repo.meego.com/MeeGo/devel/n900/repo/arm/os)  is broken.  So where can 
I get the latest kickstart file  or the latest repo url?
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] where to get the latest kickstart (.ks) file

[Adam . Mikuta]

Try: http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages

Best regards,
Adam


From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of gw zhang
Sent: Wednesday, August 25, 2010 10:34 AM
To: meego-dev@meego.com
Subject: [MeeGo-dev] where to get the latest kickstart (.ks) file

Hi All,
I don't know where to post this question, I hope I post it in the right 
place.

I follow this link 
http://wiki.meego.com/ARM/Creating_ARM_image_using_MeeGo_Image_Creator#Get_and_install_MeeGo_Image_Creator_code
 to run image creator, but after I download kickstart from 
http://repo.meego.com/MeeGo/devel/n900/images/,  The repo url 
(http://repo.meego.com/MeeGo/devel/n900/repo/arm/os)  is broken.  So where can 
I get the latest kickstart file  or the latest repo url?
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev