On 12/14/2010 2:38 PM, Nishanth Menon wrote:
Carsten Munk had written, on 12/14/2010 03:45 PM, the following:
btw, I think this discussion is better on meego-kernel ML.
Just noticed that http://wiki.meego.com/Core_OS_Program/Kernel_policy
Overall, meaning of upstream is confusing to me at least - in my
terminology upstream kernel == kernel.org which I think is wiki's
spirit is as well. How MeeGo kernel policy maps to kernel.org and
stable tree cycles is missing me though :( - The intent and benefits
of MeeGo kernel needing to maintain as few patches as possible is
obvious - just confusing from a kernel developer perspective - "I want
to enable MeeGo for platform X - what should I do?"
1. MeeGo will ship with one 'reference kernel', that will have one
shared codebase
between all the devices it supports (with different configuration
files). This kernel will be close to the upstream kernel with very
few patches applied to it,
and the version will be chosen by the architecture team such that the
kernel is
relatively recent, while still allowing for a reasonable
stabilization period
before a MeeGo release ships.
Today's "reference kernel" == kernel main package I believe = 2.6.35
(not exactly something we'd call recent).
in this context, assume 1.2 to ship with a 2.6.37 kernel as reference
kernel.
IMHO, relative sounds pretty much subjective in that context. What is
the criteria for selection of lets say MeeGo 1.3 "reference kernel"?
stable tree?
the architects will eventually decide that after discussion on the
architecture list. But doing very basic math on schedule and at some
dried tea-leaves... 2.6.39 would not be out of the question for 1.3,
unless Linus would be extremely late with 2.6.38, while 2.6.40 would be
on the super aggressive side.
What does this mean to today's kernel-dev and it's role in MeeGo?
the need for kernel-dev would be absorbed more or less by being able to
have the reference kernel follow upstream more aggressive,
while vendors that aren't as Linux-savy, and have a strong desire to
stay on an older kernel, now can do so.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
