linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: "linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>
Subject: Re: Embedded Linux Flag Version
Date: Tue, 9 Nov 2010 09:17:20 -0800	[thread overview]
Message-ID: <4CD98220.40806@am.sony.com> (raw)
In-Reply-To: <AANLkTikusrr073mUz3BQ3wP=y7E8WcDDayVms=PPhH8A@mail.gmail.com>

On 11/09/2010 03:19 AM, Mike Frysinger wrote:
> On Thu, Nov 4, 2010 at 18:07, Tim Bird wrote:
>> It was noted at the summit that several CE companies and embedded
>> projects will be using (or are already using) 2.6.35 for upcoming
>> products or releases. This includes Sony, Google, Meego, and Linaro. On
>> behalf of the CE Linux Forum and a number of consumer electronics
>> companies, projects and community developers, we therefore declare
>> 2.6.35 as a flag version of the kernel for embedded use. Several
>> companies will be investing in development, integration and testing of
>> this version. Entities wanting to do business with those companies would
>> therefore be well-advised to make sure their hardware, drivers and
>> enhancements work well with this version of the kernel.
> 
> wouldnt it make more sense to piggy back the extensive work going into
> the "stable" tree ?  many of the points you raise after all are the
> entire founding point of it.  plus, all the main distros form around
> that, are spending time working on that, is marked as supported for 2
> or 3 years, and there is already infrastructure/framework/process in
> place (stable@kernel.org).
> 
> so instead of picking arbitrary versions (like 2.6.35) and needlessly
> replicating the huge work load, simply declare these stable trees as
> the "flag" versions.  that means today it'd be 2.6.32.y.

The fact that this tree is already a year old, and not likely to be
brought forward for at least another 2 years is the reason we didn't
choose it this time.  Most of the high-profile, active embedded projects
are already on 2.6.35.  For companies looking to adopt a new base kernel
in the next 12 months, I don't want to have them start with a year-old
kernel.  We did consider the utility of synchronizing with the enterprise
stable tree, but the timing just didn't work too well this time around.

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Network Entertainment
=============================

  reply	other threads:[~2010-11-09 17:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 22:07 Embedded Linux Flag Version Tim Bird
2010-11-05 14:32 ` Josh Boyer
2010-11-09 11:19 ` Mike Frysinger
2010-11-09 17:17   ` Tim Bird [this message]
2010-11-09 17:25     ` Nicholas Mc Guire
2010-11-09 17:57       ` Tim Bird
2010-11-09 18:38       ` Nicolas Pitre
2010-11-10 10:16     ` Mike Frysinger
2010-11-10 17:30       ` Tim Bird

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CD98220.40806@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=vapier.adi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).