All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Rob Landley <rob@landley.net>
Cc: Glenn Henshaw <thraxisp@logicaloutcome.ca>,
	linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: Kernel boot problem on IXP422 Rev. A
Date: Fri, 13 Jun 2008 13:05:54 -0700	[thread overview]
Message-ID: <4852D322.5060400@am.sony.com> (raw)
In-Reply-To: <200806131233.50360.rob@landley.net>

Rob,

This is an excellent and concise description of the open
source perspective on the problem.  I'll add just one note below.

Rob Landley wrote:
> 1) Try to reproduce the bug under a current kernel.  (Set up a _test_ system.)

This sounds easy, but can be quite difficult.

Very often, product developers are several versions behind, with
no easy way to use the current kernel version.  For example, a
common scenario is starting with a kernel that comes with a board
(with source mind you), where the kernel came from the semi-conductor
vendor, who paid a Linux vendor to do a port, and it was
released in a time-frame relative to the Linux vendor's
product schedule.

This is how you end up having people STARTING projects today
using a 2.6.11 kernel.  (I know of many).

The real difficulty, when a developer finds themselves in
this position, is how to forward-port the BSP code necessary to
reproduce the bug in the current kernel.  Often, the code
is not isolated well enough (this is a vendor problem that
really needs attention.  If you have the BSP in patches, it
is usually not too bad to forward port even across several
kernel versions.  But many vendors don't ship stuff this way.)

The fact is, that by a series of small steps and delays by
the linux vendor, chip vendor, board vendor,
and product developer the code is out-of step.

It's easy to say "don't get in this position", but
this even happens when everyone is playing nice and actively
trying to mainline stuff.  BSP support in arch trees often
lag mainline by a version or two.

The number of parties involved here is why, IMHO, it has
taken so long to make improvements in this area.
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================


  reply	other threads:[~2008-06-13 20:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 19:35 Kernel boot problem on IXP422 Rev. A Marcus Tangermann
2008-06-12 20:04 ` Mike Frysinger
2008-06-12 21:28   ` Glenn Henshaw
2008-06-12 21:35     ` Mike Frysinger
2008-06-12 21:43     ` Craig Hollabaugh
2008-06-12 21:43     ` Alexey Zaytsev
2008-06-12 22:15     ` David Woodhouse
2008-06-13 17:33     ` Rob Landley
2008-06-13 20:05       ` Tim Bird [this message]
2008-06-15 19:17         ` Rob Landley
2008-06-13  0:13   ` Glenn Henshaw
2008-06-13  0:16 ` Greg Ungerer
2008-06-13 19:07   ` Marcus Tangermann
2008-06-14  7:17     ` Greg Ungerer
2008-06-19 17:59       ` Marcus Tangermann
2008-06-20  0:08         ` Greg Ungerer
2008-06-13  2:10 ` George G. Davis

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=4852D322.5060400@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=linux-embedded@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=thraxisp@logicaloutcome.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.