Re: [MeeGo-dev] MeeGo UX a 'universal'/'base reference' UX or not?

[Rudolf Streif]

Hi Carsten,

I will try to answer your question from an IVI point of view.

The reference UX for MeeGo IVI is a means to demonstrate the capabilities of
MeeGo and to exercise the underlying software stack. Car manufacturers, so
called OEMs, together with their suppliers will replace the UX with a
branded UX that fits the images and style of their make and models. The UX
is a differentiating factor for them that ties into the design of the
vehicle.

Commonly, OEMs today use the same or a very similar UX for IVI systems in
all of the models. That has to do with brand recognition as well as with
economies of scale imposed by their current product development models.
However, with a platform where the UX can easily be changed without huge
cost it is quite likely that different models of the same manufacturer will
have different UX's. A sedan targeted for business users will have a UX that
is conducive to communication, business services, etc. A family van may have
UX that is geared towards entertainment. A vehicle marketed to young drivers
may have a UX that facilitates social networking.

There is a catch-22 for the reference UX. Since the reference UX is what
potential users and evaluators of MeeGo will see first it has to be sleek
and capable enough to convincingly convey the message that MeeGo is a
capable and powerful OS for mobile connected devices. Hence, it has to
evolve continuously with the capabilities of the underlying software stack.
On the other hand it needs to leave room for imagination and improvements.
Otherwise it will hamper the adoption of MeeGo because the room for
differentiation will be too little.

:rjs

On Wed, Jun 15, 2011 at 9:59 AM, Carsten Munk  wrote:

> Hi,
>
> So, there seems to be a bit of confusion if "MeeGo UX"  (as manifested
> by the components, reference applications, design, etc) is supposed to
> be a base reference UX for all/most verticals (IVI, Handset, Tablet
> and even Netbook was proposed in a mailing list thread). The naming
> would imply that - as well as that I believe IVI is using the
> components too/apps?
>
> Can someone help provide a straight answer on what exactly reference
> UX plans are (from design team, architecture, program management or
> whoever)? Representatives from design team doesn't seem to think of
> MeeGo UX design as anything beyond tablet[1] (thanks to Ned for
> engaging us and discussing a difficult topic), so confusion is total
> by now.
>
> I personally see good potential in the MeeGo UX (as defined above) on
> many different verticals, but let's get the story straight, please -
> so we can collaborate and contribute easier. Right now 1.3 seems like
> a totally unknown road besides the Wayland plans and the EDS/Security
> stuff - let's get some roadmaps on the table for UI side too.
>
> BR
> Carsten Munk
>
> [1] https://bugs.meego.com/show_bug.cgi?id=19019#c11
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
> http://wiki.meego.com/Mailing_list_guidelines
>



-- 
*Rudolf J. Streif*
Director of Embedded Solutions
The Linux Foundation

rudolf.str...@linuxfoundation.org
Mobile: +1 858 583 1683
Skype: rudolfstreif

Linux Foundation Events Schedule:  events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org

Join us this year in celebrating the 20th Anniversary of Linux!

Watch the "Story of Linux" here:
http://www.youtube.com/watch?v=5ocq6_3-nEw

See all of the 20th Anniversary activities here:
http://www.linuxfoundation.org/20th
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Re: [MeeGo-dev] MeeGo Compliance, specifically IVI

[Rudolf Streif]

>
> Hypothetically, what about a device that doesn't fit into any of these
> categories? What if it doesn't have a traditional
> "display"/"touchscreen"/"mouse"/"ivi-scrollwheel"/etc. or what if the
> human interface is remote, over a network, or implemented entirely over
> audio? What if the device looks like clothing, a wristwatch, a wall-wart
> or "black box" or audio component, a video camera, or a portable music
> player?
>

Deducting from section "2.5.1 MeeGo API" of the compliance spec a
device without a screen cannot be MeeGo Core compliant:

"Implementations must support MeeGo API. The MeeGo API consists of the
following:
   * Qt 4.7 [Qt47]
   * Qt Mobility 1.0 [QtMob]
   * Open GL ES 2.0 [OGLES] (ARM) or OpenGL [OGL] (Atom)"

Even if you could include this API with a screen-less device and hence
technically could call it "MeeGo Core compliant" it would not make
much sense since the API is mostly useless. Further down in section
4.1 the hardware requirements for the netbook profile explicitly
specify a screen with a minimum resolution.

If the screen is implemented remotely and a required component of the
device then I suppose it could be called MeeGo compliant.

Nevertheless, the point is not to hairsplit the compliance spec. The
idea of the compliance spec is to provide a reliable basis for an
application ecosystem so that application developers can rely on a
certain set of functionality, APIs and ABIs. It forms an agreement and
if it is interpreted too loosely it defeats the purpose. Hence common
reason and judgement should be used.

>
> What is the compliance profile of http://www.cyberstep.com/kdj/ ?? (its
> based on IVI UX according to gabrbedd in #meego -- and i guess it
> qualifies as IVI if you're riding the bus or train with one :-) ).

I would not think that there is a requirement that a device has to fit
into just one category. Beyond being MeeGo Core compliant a device
could potentially also adhere to one or more device profile compliance
specifications. However, while device profile specs are in addition to
the core spec they cannot conflict the core spec but individual device
profile specs could potentially have conflicting requirements.


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

Re: [MeeGo-dev] How to create account on build.meego.com

[Rudolf Streif]

Hi,

Please check out http://wiki.meego.com/Build_Infrastructure and from there
http://wiki.meego.com/Build_Infrastructure/Packagers_Developers#How_to_get_started
for
details on how to work with the MeeGo Build System.

Dependent on what you are looking to do an account for the community build
system may be the right choice:
http://wiki.meego.com/Build_Infrastructure/Community_Builder.

BR,
:rjs

On Tue, May 3, 2011 at 8:40 PM, Yuan, Feng  wrote:

> Hello,
>
> Is there anyone who know how to create a account on *
> http://build.meego.com*? I have my account to login www.meego.com but that
> doesn’t work on build.meego.com. There is no ‘Register’ button in the
> Meego Build Service Webpage. Anyone can help me or know whom I should
> contact?
>
> Thanks in advance.
>
>
>
> Regards,
>
> Wind
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
> http://wiki.meego.com/Mailing_list_guidelines
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Re: [MeeGo-dev] Customizing & Building MeeGo Image on local system

[Rudolf Streif]

Hi Vyankatesh,

You can find an intro into MeeGo OBS here:
http://wiki.meego.com/Build_Infrastructure. That won't answer all your
questions but some.

In response to your questions below:

-Can you provide detail step (some Reference URL) regarding how to use
OBS Server, bcoz I am new to OBS.

The link above and the links branching from there can get you started. I am
currently writing 3 whitepapers on OBS that will be published on the Linux
Foundation's website some time after the LF Collaboration Summit next week.

-Can I install OBS server on Ubuntu  as Development platform ?

Technically yes but you would have to install all components manually step
by step which is quite some work. The best way is to use an OBS appliance
which is an openSUSE image with OBS on it and run it in a VM such as
VirtualBox on Ubuntu. I am doing that on my box which is Ubuntu.

-As you suggested not to build code, but my requirement is I would like
to have complete source code of MeeGo alongwith it's build enviornment so
that
I can customize it at low level (replacing UI, Kernel, middleware)

You are working for Bosch Automotive? I understand where you are coming from
and why you need that. You can load your OBS with the MeeGo sources and
build everything from scratch (well kind of, you have to bootstrap the
toolchain). We can take this offline. You will need to setup OBS
infrastructure first and get your feet wet with it.

-Then build it for other platform (cross-platform) like ARM.

Yes, MeeGo OBS has all the necessary toolchain components to build for
armv5el and armv7el.


BTW, the Linux Foundation offers on-site OBS training (now I probably will
get flagged for spamming the mailing list):
http://training.linuxfoundation.org/courses/meego/building-meego.

Rudi


On Thu, Mar 31, 2011 at 5:28 AM, Vyankatesh VD
wrote:

> Carsten Munk  writes:
>
> >
> > On Thu Mar 31 2011 11:09:54 AM CEST, Vyankatesh VD 
> in.bosch.com> wrote:
> >
> > >
> > > Hi,
> > >
> > > I want to download source packages of MeeGo and build it on my
> local
> > > machine   running Ubuntu operating system.Please provide details of
> > > procedure for doing so.
> > > do I need to use OBS(open suse build services) for building
> MeeGo
> > > Image.I want to
> > > customize MeeGo, I want to remove UI and use my own. Please
> assist
> > > on how to customize MeeGo.After customization I want build it for ARM.
> > > Pls provide details.   I am very new in Linux, aslo provide URL
> where
> > > to get source code.
> > Hi,
> >
> > You indeed need OBS but I would advise against building complete MeeGo.
> In
> most cases you don't need or want to.
> >
> > You need a workflow around these lines:
> > * set up a OBS server for your development work
> > * try to create a image for your target with MeeGo image creator using a
> kickstart file (.ks)
> > * Remove the package groups the UI consists of, from the .ks file
> > * develop your customizations with OBS, resulting in repositories that
> you can
> add with 'repo' lines in the .ks
> > * add your customization package names to %packages section of the .ks
> > * build a new image with your new .ks
> > * enjoy the result
> >
> > (repeat last 4 steps as needed)
> >
> > /Carsten
> > >
> > > Thanks,
> > > Vyankatesh
> > >
> > >
> > >
> > > ___
> > > MeeGo-dev mailing list
> > > MeeGo-dev  meego.com
> > > http://lists.meego.com/listinfo/meego-dev
> > > http://wiki.meego.com/Mailing_list_guidelines
> >
> > ___
> > MeeGo-dev mailing list
> > MeeGo-dev  meego.com
> > http://lists.meego.com/listinfo/meego-dev
> > http://wiki.meego.com/Mailing_list_guidelines
>
> Hi Carsten,
>
> Thank you very much for posting reply to my post.
> but I have few doubt.
>
> -Can you provide detail step (some Reference URL) regarding how to use
> OBS Server, bcoz I am new to OBS.
> -Can I install OBS server on Ubuntu  as Development platform ?
> -As you suggested not to build code, but my requirement is I would like
> to have complete source code of MeeGo alongwith it's build enviornment so
> that
> I can customize it at low level (replacing UI, Kernel, middleware)
> -Then build it for other platform (cross-platform) like ARM.
>
> Appreciating your assistance.
>
> With Best Regards,
> Vyankatesh
>
>
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
> http://wiki.meego.com/Mailing_list_guidelines
>



-- 
*Rudolf J. Streif*
Director of Embedded Solutions
The Linux Foundation

rudolf.str...@linuxfoundation.org
Mobile: +1 858 583 1683
Skype: rudolfstreif

Linux Foundation Events Schedule:  events.linuxfoundation.org
Linux Foundation Training Schedule: training.linuxfoundation.org
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wik

Re: [MeeGo-dev] Problem in setting up OBS

[Rudolf Streif]

John,

What did you use to setup your local OBS? An appliance image? Are you
setting it up on a dedicated box or inside a VM? Are you actually using the
IP address of your box or the hostname? Also try adding the hostname that
the appliance has to /etc/hosts. The appliance sets up the hostname in the
Ruby scripts of the web interface.

Best regards,
Rudi

On Tue, Feb 8, 2011 at 8:04 AM, john pratss  wrote:

> Hi All,
>
> I am trying to set up the OBS *with drop 1.1 latest* using
> http://wiki.meego.com/User:Stskeeps/10_easy_steps_to_a_local_OBS.
>
> I am unable to connect to the web interface for my locally set OBS (
> http://IP/ --> 500 - Internal Server Error) and as well as to repository (
> http://IP:82/   --> 404 - Not Found).
> But I am able to access the API interface using http://IP:81/.
>
> Please let me know if I am doing something wrong.
>
> Cheers,
> John
>
>
> ___
> 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] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

[Rudolf Streif]

I understand your concerns about Broadcom's open-source policy. However,
since I was successfully able to build the very same driver on the MeeGo 1.1
release form October but not with the one from 1/25 the not so far fetched
conclusion is that something changed in MeeGo. Which I now know it did.

Ok, this may not be the right list but one is probably more likely to get an
answer about init_MUTEX on a developer list than on an end-user list.

On Tue, Feb 1, 2011 at 12:58 PM, Arjan van de Ven wrote:

> On 2/1/2011 12:57 PM, Rudolf Streif wrote:
>
>> Thank you. Yes, I did download the latest source from
>> http://www.broadcom.com/support/802.11/linux_sta.php. The version number
>> is 5.100.82.38 which is the version of the spec file. It's the one I am
>> having issues with.
>>
>
> not to be an ass about it, but I would suspect that Broadcom is in a much
> better position to support their binary driver
> than the MeeGo development list Have you tried asking Broadcom for
> support instead ?
>
> (never mind that this is a development list not an end user help list)
>
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

[Rudolf Streif]

Thank you. Yes, I did download the latest source from
http://www.broadcom.com/support/802.11/linux_sta.php. The version number is
5.100.82.38 which is the version of the spec file. It's the one I am having
issues with.

Rudi

On Tue, Feb 1, 2011 at 12:27 PM, Sergio Schvezov wrote:

>  On Mon, 2011-01-31 at 22:39 -0800, Shane Bryan wrote:
>
> On Mon, Jan 31, 2011 at 05:37:51PM -0800, Rudolf Streif wrote:
> > I am trying t build the pita Broadcom WL driver module on a MeeGo Netbook
> > for which I built the image using meego-netbook-ia32-1.1.90.0.20110125.3.ks.
> > When compiling the wl_linux.c it throws "implicit declaration of function
> > 'init_MUTEX'". I installed the kernel headers and supposedly that macro is
> > declared in semaphore.h. I built that driver on previous MeeGo Netbook
> > releases but it won't compile on this one. I am not a kernel hacker, so if
> > this is obvious, please forgive me.
>
> init_MUTEX was dropped in 2.6.37 kernel
>
> Grab the src.rpm from slain.org[1] and extract the Mutex and semaphore
> patches from that (or, just use his rpm).
>
>
>
> You might need to update to the latest broadcom source as the one linked
> there is not avail anymore. Just search broadcom for that driver name as
> specified in the spec file
>
>
>  Shane...
> [1] http://slaine.org/_slaine/Meego_1.1_Wifi.html
>
>
>
> ___
> 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

[MeeGo-dev] Broadcom WL on MeeGo Netbook 1.1.90.0.20110125

[Rudolf Streif]

I am trying t build the pita Broadcom WL driver module on a MeeGo Netbook
for which I built the image using meego-netbook-ia32-1.1.90.0.20110125.3.ks.
When compiling the wl_linux.c it throws "implicit declaration of function
'init_MUTEX'". I installed the kernel headers and supposedly that macro is
declared in semaphore.h. I built that driver on previous MeeGo Netbook
releases but it won't compile on this one. I am not a kernel hacker, so if
this is obvious, please forgive me.

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

Re: [MeeGo-dev] [MeeGo-SDK] [Security part of the meego1.1]

[Rudolf Streif]

What other information/documentation on the security framework besides the
MeeGo conference slides and the basic SMACK documentation is available?

What I am looking for is how can I test the security framework by writing a
simple application that tries to do an open/iotcl on a device it does not
have access to? Is there any documentation that outlines the steps for
application developers?

Is there documentation available how the security framework should be
configured on a device so that 3rd party applications essentially cannot
access system resources via direct calls into system libraries but only
through the SDK?

Thanks,
Rudi

On Tue, Jan 18, 2011 at 7:51 PM, Ryan Ware  wrote:

> On Jan 18, 2011, at 5:23 PM, yfengying wrote:
>
> > Hi All:
> >
> > in meego1.0 release, security is not a part of it, so I want to know
> does security is part of meego1.1,
> >
> > in the rpm list of meego1.1, i not found any rpms which group name is
> "Security",
> >
> > if it has, i want to know how can i get them or their names?
>
> MeeGo 1.1 includes standard Linux security solutions.  MeeGo 1.2 will
> include a full security framework.  There is more information on what will
> be included in 1.2 here (
> http://conference2010.meego.com/session/mobile-simplified-security-framework-overview
> ).
>
> Ryan
> ___
> 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 1.2 Roadmap?

[Rudolf Streif]

No, anyone can probably request features but the link to do so is tucked
away at the end of the page where it may not be found by everybody. However,
I am only making this assumption based on finding features classified as
bugs.

Yes, that works that way. I selected Status = Feature and that does not seem
to work. No problem.

Thanks,
:rjs


On Mon, Jan 3, 2011 at 9:40 AM, Hindman, Gavin wrote:

>  I can’t log in as anyone but myself, for obvious reasons, so I’m not sure
> what you mean by your first comment – are you saying that users with the
> lowest level of access cannot file feature requests?  If so, that’s a bug in
> the tool and should be submitted as such.
>
>
> As for the search, if you’re selecting a Classification of MeeGo Features
> in the Advanced Search, you’ll only get features returned – I do this every
> day.  Additionally, all features have the string [FEA] in the Summary, so
> that can be included in the Quick Find search box if you only want to get
> features.
>
> __
> Gavin Hindman
> SSG\OTC MeeGo Core Product Manager
>
>
>
>
>
> *From:* rudolf.str...@gmail.com [mailto:rudolf.str...@gmail.com] *On
> Behalf Of *Rudolf Streif
> *Sent:* Monday, January 03, 2011 9:35 AM
> *To:* Hindman, Gavin
> *Cc:* quim@nokia.com; cars...@maemo.org; meego-dev@meego.com;
> sami.pienim...@nokia.com; ville.lavon...@nokia.com
>
> *Subject:* Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
>
>
>
> Does not seem to work too well. Most folks won't see the feature link on
> the bottom of the "New" page and at least for me searching for features
> using the advanced search function also returns all bugs even though I
> explicitly selected Features only.
>
>
>
> :rjs
>
> On Mon, Jan 3, 2011 at 9:12 AM, Hindman, Gavin 
> wrote:
>
> Bugs and features are filed under separate classifications – MeeGo Platform
> vs MeeGo Features -  there are no bugs in MeeGo Features.
>
>
>
> ______
> Gavin Hindman
> SSG\OTC MeeGo Core Product Manager
>
>
>
> *From:* rudolf.str...@gmail.com [mailto:rudolf.str...@gmail.com] *On
> Behalf Of *Rudolf Streif
> *Sent:* Monday, January 03, 2011 8:56 AM
> *To:* quim@nokia.com
> *Cc:* cars...@maemo.org; meego-dev@meego.com; Hindman, Gavin;
> sami.pienim...@nokia.com; ville.lavon...@nokia.com
>
>
> *Subject:* Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
>
>
>
> Unfortunately, the MeeGo Bugzilla does not offer a field to distinguish
> between a bug and a feature. That's something that should be considered
> adding.
>
>
>
> For MeeGo IVI I have searched the database and compiled a list:
>
>
>
> Bugzilla ID Title
>
> 7668[FEA] Multi Screen Support
>
> 7669[FEA] Tethered Device Indexing
>
> 7670[FEA] Multi Zone Audio
>
> 7671[FEA] Distributed Audio Management
>
> 7672[FEA] Network Gateway
>
> 7674[FEA] Phonebook Sync with CE Device
>
> 7675[FEA] Media Sync with home PC
>
> 7677[FEA] Multi-User Support
>
> 7678[FEA] IVI Fastboot
>
> 7679[FEA] Persistency Management
>
> 7680[FEA] Power Management
>
> 7681[FEA] System Health Monitor
>
> 7682[FEA] Inertia based Application control
>
> 8704[FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI
>
> 8813[FEA] Terminal Mode VNC Client
>
> 8814[FEA] Remote Framebuffer Protocol
>
> 8815[FEA] Integrate EMGD 1.0 Update user mode driver components
>
> 8816[FEA] RFB Encodings
>
> 8817[FEA] Terminal Mode 1.0 RFB extension messages
>
> 8818[FEA] Terminal Mode UpnP Control Point
>
> 8819[FEA] IVI document viewer
>
> 8821[FEA] TmServerDevice:1 Device
>
> 8822[FEA] IVI Nobody
>
> 8823[FEA] Terminal Mode Audio
>
> 8824[FEA] IVI Proximity
>
> 8827[FEA] IVI Persistancy Control Manager
>
> 8828[FEA] RTP Client supporting Terminal Mode payload
>
> 8829[FEA] Terminal Mode Client Controller
>
> 9169[FEA] Contacts should have routing integration
>
> 9171[FEA] Weather app
>
> 9174[FEA] Media player: FM/AM radio
>
> 9175[fEA] MCP pluggable mass storage controls
>
> 9209[FEA] btrfs compression during installation
>
> 9210[FEA] Remove physical keyboard requirement
>
> 9211[FEA] Enhance meego-handset-songs to a classed audio sources
>
> 9212[FEA] Sample Sirius radio integration
>
> 9213[FEA] Rebase Russellville tsc2007 touchscreen to evdev
>
> 10295  [FEA] Request for Bluetooth DUN support for both server and client
> role
>
> 10355  [FEA] UI should include a day/night mode
>
> 11256  [FEA] Over-the-Air 

Re: [MeeGo-dev] MeeGo 1.2 Roadmap?

[Rudolf Streif]

Does not seem to work too well. Most folks won't see the feature link on the
bottom of the "New" page and at least for me searching for features using
the advanced search function also returns all bugs even though I explicitly
selected Features only.

:rjs

On Mon, Jan 3, 2011 at 9:12 AM, Hindman, Gavin wrote:

>  Bugs and features are filed under separate classifications – MeeGo
> Platform vs MeeGo Features -  there are no bugs in MeeGo Features.
>
>
>
> __
> Gavin Hindman
> SSG\OTC MeeGo Core Product Manager
>
>
>
> *From:* rudolf.str...@gmail.com [mailto:rudolf.str...@gmail.com] *On
> Behalf Of *Rudolf Streif
> *Sent:* Monday, January 03, 2011 8:56 AM
> *To:* quim@nokia.com
> *Cc:* cars...@maemo.org; meego-dev@meego.com; Hindman, Gavin;
> sami.pienim...@nokia.com; ville.lavon...@nokia.com
>
> *Subject:* Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
>
>
>
> Unfortunately, the MeeGo Bugzilla does not offer a field to distinguish
> between a bug and a feature. That's something that should be considered
> adding.
>
>
>
> For MeeGo IVI I have searched the database and compiled a list:
>
>
>
> Bugzilla ID Title
>
> 7668[FEA] Multi Screen Support
>
> 7669[FEA] Tethered Device Indexing
>
> 7670[FEA] Multi Zone Audio
>
> 7671[FEA] Distributed Audio Management
>
> 7672[FEA] Network Gateway
>
> 7674[FEA] Phonebook Sync with CE Device
>
> 7675[FEA] Media Sync with home PC
>
> 7677[FEA] Multi-User Support
>
> 7678[FEA] IVI Fastboot
>
> 7679[FEA] Persistency Management
>
> 7680[FEA] Power Management
>
> 7681[FEA] System Health Monitor
>
> 7682[FEA] Inertia based Application control
>
> 8704[FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI
>
> 8813[FEA] Terminal Mode VNC Client
>
> 8814[FEA] Remote Framebuffer Protocol
>
> 8815[FEA] Integrate EMGD 1.0 Update user mode driver components
>
> 8816[FEA] RFB Encodings
>
> 8817[FEA] Terminal Mode 1.0 RFB extension messages
>
> 8818[FEA] Terminal Mode UpnP Control Point
>
> 8819[FEA] IVI document viewer
>
> 8821[FEA] TmServerDevice:1 Device
>
> 8822[FEA] IVI Nobody
>
> 8823[FEA] Terminal Mode Audio
>
> 8824[FEA] IVI Proximity
>
> 8827[FEA] IVI Persistancy Control Manager
>
> 8828[FEA] RTP Client supporting Terminal Mode payload
>
> 8829[FEA] Terminal Mode Client Controller
>
> 9169[FEA] Contacts should have routing integration
>
> 9171[FEA] Weather app
>
> 9174[FEA] Media player: FM/AM radio
>
> 9175[fEA] MCP pluggable mass storage controls
>
> 9209[FEA] btrfs compression during installation
>
> 9210[FEA] Remove physical keyboard requirement
>
> 9211[FEA] Enhance meego-handset-songs to a classed audio sources
>
> 9212[FEA] Sample Sirius radio integration
>
> 9213[FEA] Rebase Russellville tsc2007 touchscreen to evdev
>
> 10295  [FEA] Request for Bluetooth DUN support for both server and client
> role
>
> 10355  [FEA] UI should include a day/night mode
>
> 11256  [FEA] Over-the-Air (OTA) Updates
>
> [FEA-IVI-UX] Align IVI Home Screen with MeeGo Touch direction
>
> [FEA-IVI-UX] Unified Media Player
>
> [FEA-IVI-UX] Unified Dialler
>
> [FEA-IVI-UX] Navigation
>
> [FEA-IVI-UX] Document Viewer
>
> [FEA-IVI-UX] Picture Viewer
>
> [FEA-IVI-UX] Speech recognition
>
>
>
> The MeeGo IVI Working Group has identified the following high-level areas
> for the near-term roadmap:
>
>
>
> • App Store Demonstration
>
> • Automotive Networking
>
> • Audio management
>
> • Device connectivity
>
> • Navigation
>
> • Auto UX
>
> • BSP/ARM-support
>
>
>
> We are currently in process of fleshing them out. I will put this framework
> up on the IVI roadmap page on meego.com.
>
>
>
> :rjs
>
>
>
> On Mon, Jan 3, 2011 at 2:47 AM,  wrote:
>
> Hi there,
>
>
> Carsten wrote:
> > So, we're in 2011, we have a release 1.2 in about 4-5 months - and I
> > wondered, what do we intend on delivering?
>
> See, comment, vote:
>
> Bug 9908 - Open roadmapping process defined but no implemented
> http://bugs.meego.com/show_bug.cgi?id=9908
>
> I also think this is an important topic and I also expected more
> information or at least feedback from the roadmap owners at this point.
>
>
> > I went to http://wiki.meego.com/Roadmap and looked, finding that we
> > have a release plan (always g

Re: [MeeGo-dev] MeeGo 1.2 Roadmap?

[Rudolf Streif]

Unfortunately, the MeeGo Bugzilla does not offer a field to distinguish
between a bug and a feature. That's something that should be considered
adding.

For MeeGo IVI I have searched the database and compiled a list:

Bugzilla ID Title
7668 [FEA] Multi Screen Support
7669 [FEA] Tethered Device Indexing
7670 [FEA] Multi Zone Audio
7671 [FEA] Distributed Audio Management
7672 [FEA] Network Gateway
7674 [FEA] Phonebook Sync with CE Device
7675 [FEA] Media Sync with home PC
7677 [FEA] Multi-User Support
7678 [FEA] IVI Fastboot
7679 [FEA] Persistency Management
7680 [FEA] Power Management
7681 [FEA] System Health Monitor
7682 [FEA] Inertia based Application control
8704 [FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI
8813 [FEA] Terminal Mode VNC Client
8814 [FEA] Remote Framebuffer Protocol
8815 [FEA] Integrate EMGD 1.0 Update user mode driver components
8816 [FEA] RFB Encodings
8817 [FEA] Terminal Mode 1.0 RFB extension messages
8818 [FEA] Terminal Mode UpnP Control Point
8819 [FEA] IVI document viewer
8821 [FEA] TmServerDevice:1 Device
8822 [FEA] IVI Nobody
8823 [FEA] Terminal Mode Audio
8824 [FEA] IVI Proximity
8827 [FEA] IVI Persistancy Control Manager
8828 [FEA] RTP Client supporting Terminal Mode payload
8829 [FEA] Terminal Mode Client Controller
9169 [FEA] Contacts should have routing integration
9171 [FEA] Weather app
9174 [FEA] Media player: FM/AM radio
9175 [fEA] MCP pluggable mass storage controls
9209 [FEA] btrfs compression during installation
9210 [FEA] Remove physical keyboard requirement
9211 [FEA] Enhance meego-handset-songs to a classed audio sources
9212 [FEA] Sample Sirius radio integration
9213 [FEA] Rebase Russellville tsc2007 touchscreen to evdev
10295 [FEA] Request for Bluetooth DUN support for both server and client
role
10355 [FEA] UI should include a day/night mode
11256 [FEA] Over-the-Air (OTA) Updates
[FEA-IVI-UX] Align IVI Home Screen with MeeGo Touch direction
[FEA-IVI-UX] Unified Media Player
[FEA-IVI-UX] Unified Dialler
[FEA-IVI-UX] Navigation
[FEA-IVI-UX] Document Viewer
[FEA-IVI-UX] Picture Viewer
[FEA-IVI-UX] Speech recognition

The MeeGo IVI Working Group has identified the following high-level areas
for the near-term roadmap:

• App Store Demonstration
• Automotive Networking
• Audio management
• Device connectivity
• Navigation
• Auto UX
• BSP/ARM-support

We are currently in process of fleshing them out. I will put this framework
up on the IVI roadmap page on meego.com.

:rjs

On Mon, Jan 3, 2011 at 2:47 AM,  wrote:

>  Hi there,
>
> Carsten wrote:
> > So, we're in 2011, we have a release 1.2 in about 4-5 months - and I
> > wondered, what do we intend on delivering?
>
> See, comment, vote:
>
> Bug 9908 - Open roadmapping process defined but no implemented
> http://bugs.meego.com/show_bug.cgi?id=9908
>
> I also think this is an important topic and I also expected more
> information or at least feedback from the roadmap owners at this point.
>
> > I went to http://wiki.meego.com/Roadmap and looked, finding that we
> > have a release plan (always good..) and plans related to the build
> > infrastructure.. But no Core/Handset/IVI/SDK roadmaps. Nor on
> > meego.com anywhere.
> >
> > The question is - and I think it's a fairly reasonable one: Where is
> > our Core, Handset, Netbook, IVI and SDK roadmaps for 1.2? It's not on
> > meego.com anywhere - how does our future platform 'customers' know
> > what we plan to have coming for MeeGo 1.2?
> >
> > And second: What is the current status of them - where can I see the
> > work in progress? Is there some featurezilla searches?
> >
> > Gavin, Sami, Rudolf, Ville and the rest of you guys responsible for
> > MeeGo roadmaps - could I ask you to spend some few minutes elaborating
> > to the rest of the project what's going on in Program Office regarding
> > the roadmaps for 1.2 for your areas? It'll help people understand why
> > these roadmaps may be missing and set up expectations to when we'll
> > see them :)
>
> --
> Quim
>
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] [MeeGo-community] PCWorld: Why Nokia Is in Deep Trouble With MeeGo (should someone reply to this article?)

[Rudolf Streif]

There is no use in responding to such an article. It shows rather
opinionated journalism using mostly language of affection rather than
language of report.

Netscape's demise had nothing to do with its technology and/or with making
it open source but with the business model and marketing. AOL open-sourced
the software because there was no need for them anymore to develop and
provide their own browser after Microsoft started bundling their browser
with their OS.

I also find it interesting that the author states "God help any corporation
that relies on open source to deliver the goods quickly." but later
claims "Android
is the future. There isn't any question." Android may not be open-source
itself but it it most certainly built on it.

Noteworthy is also this statement of the author: "It'll be game over for any
other competitor because history has shown that most technology marketplaces
only support two main players." First of all he fails to mention any cases
of history and why they would be applicable to this situation. Secondly, he
implies that even if there is only room for two major players in the
marketplace that the first two will prevail. That is definitely not the
case. Better technology that offers more value to its users will eventually
prevail. That is essentially what Dominique is saying. It is in the hands of
the MeeGo developers to create this value through delivering on new ideas.

Like any technology MeeGo is moving along the well known and understood
S-curve. At this moment it is in the early stage where its capabilities are
lacking behind current other technologies and progress seems slow. However,
eventually it will be able to catch up, accelerate and surpass them if there
is sufficient driving force behind it. Exactly because of its openness MeeGo
is very exposed since it is very visible that it is not quite ready yet. iOS
and Android went through the exact same stages but it happened behind closed
doors not visible to the outside. However, MeeGo's potential can be far more
reaching because it collects input and ideas from many more smart people at
a very early stage. Nevertheless, MeeGo's challenge is to harness that
potential and focus the energy on its development. Consequently, it is not
worth wasting any energy on responding to such articles since there will be
many more but the energy is better utilized to deliver on MeeGo's vision.

Rudi


On Wed, Dec 22, 2010 at 1:14 PM, Randolph Dohm wrote:

> 2010/12/22 Dominig ar Foll :
> > Le 22/12/2010 06:43, a.gra...@gmail.com a écrit :
> >> Hi,
> >>
> >> I imagine you all have read this:
> >>
> http://news.yahoo.com/s/pcworld/20101208/tc_pcworld/whynokiaisindeeptroublewithmeego
> >> How could we reply to this? We simply ignore? We take an official
> position?
> >>
> >>
> > Hello,
> >
>  Then you have to deal
> > with Fashion waves.
> >
>  in the last 10 years I have
> > seens Nokia be cool, then Moto be hot, then an iPhone was require to be
> in.
> > The iPhone is now starting be consider off by the young generation who
> > are moving to the next hot things (currently Android). Blackberry, in
> > particular with Girls, has resisted very well compare to other type of
> > smart phones (e.g. Windows).
>
>
>
> I disagree, today it is not the fashion of the mobile phone brand, it
> is the fashion of the operating system on the smartphone.
> Android is getting more popular each day. in some days we have a
> tipping point, the threadstarter compares with netscape´s  second
> awake at AOL. Indeed, meego needs a hardware working on it, and that
> needs a release date.
> Nokia and Trolltech and the symbian developers have enough manpower to
> work on meego. They need a HR department restructuring the personnel
> to work on and coordinate meego. it can´t be so hard to get in each
> team two persons more to push a meego release with a phone (left or
> right the nokia n900 product cyclus phase..). Dont wait for n900
> return on invest and oversleep the tipping point for a meego release..
>
> Quim, when will there be a mobile phone with meego released? Please
> announce a date or announce a date, when you will announce a date.
> Or is it true, that you will leave nokia too?
>
> Regards Randolph
> ___
> MeeGo-community mailing list
> meego-commun...@meego.com
> http://lists.meego.com/listinfo/meego-community
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Urgent: We need community ftp space or similar

[Rudolf Streif]

I second Joel's motion. A ready to go image is good to get people
jumpstarted but eventually we need the full infrastructure and a responsible
maintainer. There are also different revisions of the Beagle and some known
issues with graphics and acceleration. These are barriers of entry and need
to be made transparent.
Rudi

On Dec 1, 2010 8:28 AM, "Clark, Joel"  wrote:



Carsten Munk wrote:
>2010/12/1 Clark, Joel :
>>
>>
>>

>> Why don't you fold your work back into the build process so the images
are produced under >>http:...
>BR
>Carsten Munk

First we need someone to be the image maintainer for the beagleboard.
Someone to own bugs found. If Till is building images to share with the
community then please just go the next step and agree to maintain that
image, so we can leverage the existing build and bugs infrastructure to
support the beagleboard community.I don't believe there is significant
additional "needed MeeGo bureaucracy".  2 or 3 folks would be nice but 1
person could do it.  What is needed is a kernel maintainer for beagleboard,
platform maintainer for beagleboard, and someone to ensure the build scripts
(i.e. kickstart) is right and the resulting images actually  boots. Sure it
would be nice to have a full QA team dedicated to the board, but the
community can provide that capability and file any bugs found.  But someone
has to own the bugs found.
Let's use the processes already in place rather than fork off a whole new
process.

regards
Joel


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

Re: [MeeGo-dev] ambient noise sensing

[Rudolf Streif]

Hi Alison,

This is certainly possible. The challenge is to distinguish ambient noise
from conversations and avoiding positive feedback loops. Good filter
algorithms are mandatory.

IVI  currently uses a much simpler but mostly adequate solution. For decades
car radios have been equipped with an input for the alternator's speed
signal. The faster the engine cranks the higher the frequency of the signal.
Nowadays cars have digital instruments for engine rev and vehicle speed and
the IVI systems get the data through the vehicle buses and adjust volume
accordingly.

It is an excellent example how sensor signals combinef with policies will
affect audio management in a car.

Rudi

On Nov 30, 2010 3:36 PM,  wrote:

  One lingering question I have from the Sensor Framework MeeGoCon
presentation is about the possible use of the microphone as a sensor.The
use of an ambient light sensor to adjust screen brightness is often
mentioned, but I've never heard anyone mention the related idea of adjusting
audio volume based on ambient noise.I particularly like the idea for the
IVI environment.I suppose that there could be privacy concerns with
turning the microphone on at random times, but if it's just for a
millisecond, the potential for snooping on the user is minimal.

>From the point of view of Tracker/Zeitgeist and the Context Framework, there
are many more subtle applications for ambient noise sensing like figuring
out if the device owner is alone or in a conversation.

-- 
Alison Chaiken
Nokia Mobility Solutions
alison.chai...@nokia.com
650-279-5600
http://www.exerciseforthereader.org/



___
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] Error: failed to create image : Failed to find package 'syslinux' : No package(s) available to install

[Rudolf Streif]

Good point, I missed that. But why does mic2 then give him the error message
"Error: failed to create image : Failed to find package 'syslinux' :
No package(s) available to install."?

Is that a bug of mic2 and can be ignored?

Rudi

On Tue, Nov 23, 2010 at 7:51 AM, Arjan van de Ven wrote:

> Hi Harsha,
>>
>> You need the right version of syslinux on your system. The best way to
>> update your system is to download the package from
>> http://repo.meego.com/MeeGo/tools/repos/ and build it. Choose your
>> distribution accordingly e.g. for Ubuntu 10.04:
>> http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/.
>>
>
> eh guys .. he's trying to make an ARM image.
> there's no syslinux involved for arm... at all.
>
>
>
>
>> Best regards,
>> Rudi
>>
>>
>> On Tue, Nov 23, 2010 at 6:27 AM, > nanjundiah.har...@elektrobit.com>> wrote:
>>
>>http://wiki.meego.com/ARM/Creating_ARM_image_using_MeeGo_Image_Creator
>>
>>sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=raw
>>--arch=armv7l --save-kernel --config=YOUR_KICKSTART
>>
>>sudo mic-image-creator --cache=mycachedir --format=raw --arch=armv7l
>>--save-kernel
>>
>>  --config=/home/harsha/workspace/image-creator-stable/meego-handset-armv7
>>l-n900-1.1.80.6.20101112.1.ks
>>
>>Issue:
>>Error: failed to create image : Failed to find package 'syslinux' : No
>>package(s) available to install.
>>
>>I tried different versions of syslinux but couldnot succeed. I tried
>>3.85, 3.86, 4.01 & 4.02 versions of syslinux package.
>>
>>Br,
>>Harsha
>>
>>
>>
>>Please note: This e-mail may contain confidential information
>>intended solely for the addressee. If you have received this
>>e-mail in error, please do not disclose it to anyone, notify
>>the sender promptly, and delete the message from your system.
>>Thank you.
>>
>>___
>>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
>>
>
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Error: failed to create image : Failed to find package 'syslinux' : No package(s) available to install

[Rudolf Streif]

Hi Harsha,

You need the right version of syslinux on your system. The best way to
update your system is to download the package from
http://repo.meego.com/MeeGo/tools/repos/ and build it. Choose your
distribution accordingly e.g. for Ubuntu 10.04:
http://repo.meego.com/MeeGo/tools/repos/ubuntu/10.04/.

Best regards,
Rudi

On Tue, Nov 23, 2010 at 6:27 AM,  wrote:

> http://wiki.meego.com/ARM/Creating_ARM_image_using_MeeGo_Image_Creator
>
> sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=raw
> --arch=armv7l --save-kernel --config=YOUR_KICKSTART
>
> sudo mic-image-creator --cache=mycachedir --format=raw --arch=armv7l
> --save-kernel
> --config=/home/harsha/workspace/image-creator-stable/meego-handset-armv7
> l-n900-1.1.80.6.20101112.1.ks
>
> Issue:
> Error: failed to create image : Failed to find package 'syslinux' : No
> package(s) available to install.
>
> I tried different versions of syslinux but couldnot succeed. I tried
> 3.85, 3.86, 4.01 & 4.02 versions of syslinux package.
>
> Br,
> Harsha
>
>
> 
> Please note: This e-mail may contain confidential information
> intended solely for the addressee. If you have received this
> e-mail in error, please do not disclose it to anyone, notify
> the sender promptly, and delete the message from your system.
> Thank you.
>
> ___
> 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] DVB support on MeeGo

[Rudolf Streif]

As I said in my earlier post most of the software required to demultiplex
and decode DVB-compliant MPEG2 transport streams is already available in
MeeGo. Gstreamer handles the demuxing of the TS and the plugins can handle
the video and audio decoding. For video it is typically MPEG-2 for standard
definition and MPEG-4 Part 10 (H.264) for high definition (sometimes also
for SD to gain bandwidth). Audio typically is AC3.

What's missing is decoding of the Service Information if required and
eventually the Teletext. Although DVB defines Teletext encoding as stream it
is not that commonly used. Many operators are still using the VBI-encoding
from the analog days and in that case the Teletext is found in the video
stream.

Most, and in particular cheap, DVB hardware does not support any demuxing
and decoding at all. It's only a tuner/demodulator. The kernel driver for
the hardware will then only allow tuning to a particular channel and then
deliver the MPEG-2 TS to the user level application.

If all you want to do is watch DVB TV on your MeeGo device all you need is
tuner/demod hardware, a character device driver for it to control it and to
read the MPEG-2 TS from.

Rudi

On Fri, Oct 29, 2010 at 2:49 PM, Nicolas Dufresne <
nicolas.dufre...@gmail.com> wrote:

>  Le vendredi 29 octobre 2010 à 13:28 -0700, Auke Kok a écrit :
>
>  I hate to say this, but the fact that "it works in ubuntu" does not mean
> anything, as there are too many applications in ubuntu that we will
> never be able to ship due to licensing restrictions etc. Is it shipped
> as part of a default unmodified upstream kernel? Does it require
> MPEG-licensed components?
>
> DVB Kernel driver does not deal with encoding/decoding MPEG unless this is
> implemented by hardware (in which case the licence is part of the hardware
> price).
>
> I think the request here is as simple as, is it possible to include DVB
> linux stack in the Linux drivers ? Getting the rest of the softwares is much
> easier task since it can be done by an independent team.
>
> regards,
> Nicolas (alias stormer)
>
> ___
> 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] DVB support on MeeGo

[Rudolf Streif]

I am afraid we are losing the focus in regards to Vijay's original question.
Vijay did not say for what type of device he is looking for DVB support from
MeeGo.

Digital television, DVB-T and ATSC, requires different antennae then analog
TV for UHF/VHF. For those the aerials had to be pointed to the transmitter.
For DTV that is typically not necessary. It is possible to receive the
signals with simple "rabbit ears" even from inside a home. However, that is
as usual dependent on environmental and other factors.

Rudi

On Thu, Oct 28, 2010 at 1:05 PM, Ross Burton  wrote:

> On Thu, 2010-10-28 at 21:40 +0200, Randolph Dohm wrote:
> > Hi Ross,
> > no, it is not about DVB-H, that is dead born, it is about DVB-T.
> > So users can watch TV without payment like in any TV.
> > That makes the success, if it is default in. Nokias Key.
>
> If I want to watch DVB-T at home I need a rather large aerial that is
> aimed at the transmitter.  How does that work on a mobile device?
>
> Ross
> --
> Intel Open Source Technology Centre
> http://oss.intel.com/
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] DVB support on MeeGo

[Rudolf Streif]

Vijay,

There is actually no simple and straightforward answer to any system
supporting Digital Video Broadcasting because it is a multilayer
architecture.

DVB uses MPEG-2 Transport Streams (MP2TS) as defined by ISO/IEC 13818-1
Systems with DVB-specific Service Information (SI) as specified in ETSI EN
300 468.

For transmission these streams are modulated onto a bearer. What the bearer
is depends on the transmission system. Hence, DVB specifies multiple
standards: DVB-S and DVB-S2 for satellite transmission, DVB-SH for satellite
transmission to handhelds, DVB-C and DVB-C2 for cable transmission, DVB-T
and DVB-T2 for terrestrial transmission, and DVB-H for terrestrial
transmission to handhelds. The standards use different modulation and
modulation schemes such as QAM, PSK, QPSK, APSK, etc. Most recently
DVB-compliant MP2TS are also used in IPTV and there the transmission is an
IP network using UDP unicast/multicast and/or TCP dependent on the
application. Sometimes for IPTV the streams are RTP-encapsulated and may
also use Quality of Experience (QE) technologies such as Cisco's VQE or
Alcatel-Lucent's FCC/RET.

Here starts the first layer of the problem. Dependent on how your MeeGo
system will receive the DVB MP2TS you will need hardware to do the
demodulation. For that you will obviously a driver, typically a character
device driver as kernel module. If your system receives the stream via IP
you are all set.

Once you got to MP2TS you will have to demultiplex it. MeeGo uses gstreamer
and one of the container formats it supports is MP2TS. After that the
elementary streams need to be decoded. Most importantly video and audio and
for that gsteamer supports a variety of codecs. If you need to be able to
decode the SI for EPG etc. in the DVB MP2TS then you will probably need a
plugin for gstreamer to decode it.

DVB television programs may be encrypted with a CA system. That adds another
layer of complexity since you wont be able to decode the elementary streams
unless they are decrypted. DVB systems mostly use transport scrambling
control meaning the payload of the MP2TS packets is encrypted. What packets
are encrypted is indicated by the 2 TSC (transport scrambling control) bits
in the MP2TS header.

Best regards,
Rudi



On Wed, Oct 27, 2010 at 10:43 PM, vijay singh  wrote:

> Hello,
> I want to know do we have support for DVB under MeeGo 1.0 or planned
> MeeGo 1.1 release.
>
> Bye--
>
> ___
> 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