On Sat, May 7, 2011 at 2:40 PM, Wichmann, Mats D <[email protected]> wrote: > [email protected] wrote: >> Hello, >> >> I'd like to discuss a specific area of compliance for IVI systems. >> Before I get to the subject matter, I'd like to know if I'm following >> the correct process so I can address the right people. My first stop >> was the MeeGo wiki where I searched for Compliance and arrived here: >> http://wiki.meego.com/Compliance_primer_draft_Feb2011 >> >> Is this the current canonical source for compliance in MeeGo? > > the up to date/approved version of that is at: > http://wiki.meego.com/Quality/Compliance_primer_1.0 > > but really, the canonical source is the compliance spec itself.
Where can I find that document? >> In that document it states "Currently MeeGo supports five different >> verticals: Netbooks, Handsets, Connected-TVs, In-Vehicle Infotainment >> systems and tablets. Each of these verticals will have a Compliance >> Profile." I take that to mean that the In-Vehicle Infotainment (IVI) >> will have a separate compliance specification. >> >> Does that mean the IVI compliance specification is independent of the >> overall MeeGo compliance specification? > > The intent is that each workgroup/vertical write (*) a layer document, > which adds on to the base compliance. Okay, so a specific vertical might "inherit" from the core compliance? Would it be possible to state this along the lines of "OpenGL ES is in MeeGo Core so using OpenGL ES in MeeGo IVI is compliant?" > At the moment the implementation > of that is a chapter in the single compliance document, describing > the profile for the vertical. There's only one instance in 1.1, > the Netbook profile, which says very little, so it's not clear to me > if that model is actually going to work long term, but let's try it. Makes sense to me. I think it is definitely worth trying since having inter-device compatibility is a significant innovation, at least on the API level. > There's a second example on the wiki, which was an initial effort at > a handset profile: > http://wiki.meego.com/Quality/Compliance/HandsetProfile Thanks, I'll look at that and propose that as an input to the IVI compliance discussion. > (*) "write" could consist of just feeding me (as the spec editor) > the appropriate information, and then doing reviews. Can I propose specific compliance packages directly to you? Obviously I'd be wearing my MeeGo IVI Release Manager hat and would have something for compliance that has received consensus in the IVI project group, but is this a reasonable description of the compliance process? >> Lastly, I'd like to know the specifics about OpenGL, particularly >> OpenGL ES. Is OpenGL ES going to be part of compliance in MeeGo IVI? > > it's going to be part of the core compliance as of 1.2. I don't > think we've envisioned a model where a vertical /removes/ any components > from the core, so that would make the answer Yes, I guess, without > knowing anything specific about IVI. The specifics are (roughly) OpenGL is used only in OpenGL ES format on ARM. This means that there can be different OpenGL "renderers" and an application written against one rendering backend will not work with another rendering backend. To reach the point where we can specify renderers, we'll need to determine if in MeeGo IVI we want to be OpenGL ES compliant or OpenGL compliant. This decision has implications for the different architectures so needs to be carefully addressed. I think it would be difficult to end up in a situation where one platform is specifying OpenGL and the other OpenGL ES in the same vertical, though it probably could be managed. > Hope this helps. Yes, a lot! Thanks. Jeremiah _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
