[Meego-porting] Adaptation interfaces?

[Jari.Palojarvi at nokia.com]

Excellent stuff. In my thinking, this basically represents the "next level" below the currently very high-level MPG info.

Only two small comments:

- Kernel framebuffer driver
    - Our (i.e. Nokia) display/graphics guys said that we might 
      not need to have this as a must requirement for 
      display/graphics adaptation (i.e. the X level would suffice)
    - But I'm OK with this if this is considered to be a sensible 
      requirement and not an unnecessary difficult burden to anyone

- Adaptation I/F types, to-replace etc.
    - This is a bit vague comment, but the current "Module API" 
      and "Image build-time replace-able API" terms could perhaps 
      be clarified a bit.
    - Something like: 
          - "Module API" _could_ be "Plugin module API" 
          - "Image build-time replace-able API" could be
            simply "Library API" (the API is not replaceable
            but the implementing library is)
          - "To-replace", "To-configure" etc. could perhaps be 
            replaced with a generic "Todo" that would then 
            describe what to do. E.g. "deliver a shared library
            called libEGL.so.1 that implements the above specified
            interface" 
      
Regards, Jari

> -----Original Message-----
> From: meego-porting-bounces at lists.meego.com [mailto:meego-porting-
> bounces at lists.meego.com] On Behalf Of ext Carsten Munk
> Sent: 26. marraskuuta 2010 12:20
> To: meego-porting at meego.com
> Subject: Re: [Meego-porting] Adaptation interfaces?
> 
> 2010/11/22 Carsten Munk <carsten.munk at gmail.com>:
> > One of the things in Jari's talk in the unconference session on
> > hardware adaptations in MeeGo was regarding adaptation interfaces in
> > the MeeGo Core OS.
> >
> > .. and I got wondering if we have a list of these in the current
> > architecture grouped by which subsystem they're in?
> >
> > Or is it something we are making up as we go?
> >
> 
> Seems like my first email didn't make it through..
> 
> I've started to map the Nokia N900 hardware adaptation in order to
> help establish what adaptation I/Fs we actually have in MeeGo. We have
> some I/Fs we probably need to clean up in 1.2. Change proposals more
> than welcome.
> 
> I've put up my initial list of I/Fs that are actually used currently
> (not complete yet) -- does this seem like a good structure to help
> define adaptation I/F'es? A clear and direct way of "how do you adapt
> this specifically on my hardware and what knobs/hooks should I use and
> are there any examples"
> 
> URL is http://wiki.meego.com/User:Stskeeps/AdaptationIF  -- comments
> more than welcome!
> 
> BR
> Carsten Munk
> _______________________________________________
> MeeGo-porting mailing list
> MeeGo-porting at lists.meego.com
> http://lists.meego.com/listinfo/meego-porting