On 12/02/2010 05:01 PM, Arjan van de Ven wrote:
On 12/2/2010 6:19 AM, Teemu Tuominen wrote:
Hello,
Please excuse me if I haven't done my home work, but...
Why isn't kernel-headers made explicitly from the kernel project, even
though its patch-set is dealing with ABI ?
because that causes major issues with OBS rebuilds. kernel-headers
change causes glibc to rebuild (and then the OS). ... this would limit
the rate at which we can do kernel updates
Well, that's a fairly good reason.
I have pondered the issue with the few example headers we have with
V4L2/MediaController API changes. So, are we currently utilizing
backported drivers and stuff, but tend to think that kernel stays ABI
compatible with older upstream version ?
the other reason is that we ONLY want to ship the OFFICIAL ABI to
applications, not an "abi" that comes from random patches added to the
kernel.
2. request kernel committers to commit kernel-headers too (and
consider how this will stay in sync)
no to either;
the only request we'll take is "can you move kernel-headers to a new
upstream version"..
if you get your ABI change accepted by Linus and then into a release, we
can get it into kernel-headers.
Ok, so lets consider the particular case with V4L2 subdev and Media
Controller API.
AFAIK all of the targeted devices containing camera are expected to
utilize those
to provide camera FEA's. API's were accepted, but we are talking about
fairly new patches
to them as well.
I assume the recent patches can be partly covered within adaptation
projects, but am afraid
that we might fail to have a common ways to utilize camera in 1.2 due this.
I'm not much experienced nor following the upstream process, so I ask
LaurentP to
provide the version details.
Thanks,
-Teemu
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
