linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: David VomLehn <dvomlehn@cisco.com>
Cc: Grant Erickson <gerickson@nuovations.com>,
	Robin Getz <rgetz@blackfin.uclinux.org>,
	Mike Frysinger <vapier@gentoo.org>,
	Greg Ungerer <gerg@snapgear.com>,
	Russell King <rmk@arm.linux.org.uk>,
	Paul Mundt <lethal@linux-sh.org>, Tim Bird <tim.bird@am.sony.com>,
	linux-embedded <linux-embedded@vger.kernel.org>,
	Hariprasad Nellitheertha <hari@in.ibm.com>
Subject: Re: Kernel crashing and log buffers...
Date: Fri, 12 Jun 2009 07:33:10 +0200	[thread overview]
Message-ID: <20090612053310.9E9D9832E416@gemini.denx.de> (raw)
In-Reply-To: <20090612003302.GA23715@cuplxvomd02.corp.sa.net>

Dear David VomLehn,

In message <20090612003302.GA23715@cuplxvomd02.corp.sa.net> you wrote:
>
> > However, the value and what's being proposed here and what I and others
> > proposed--at least in the embedded kingdom--seems high and the features and
> > implementation needn't be mutually exclusive.
> 
> I agree. In this case, we have three different approaches to three different
> problems (bootloader buffers, continuous state logging, and in-kernel capture
> of logging). All are problems that need to be solved. Personally, I'd love
> to have the continuous state logging, though I don't need the bootloader
> buffer part.

Question is: do we need three different solutions, or can we come up
with one solution that covers all?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"If it ain't broke, don't fix it."                       - Bert Lantz

  reply	other threads:[~2009-06-12  5:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  1:26 Kernel crashing and log buffers Robin Getz
2009-06-11 17:53 ` David VomLehn
2009-06-11 18:22   ` Tim Bird
2009-06-11 22:46     ` David VomLehn
2009-06-11 18:52   ` Robin Getz
2009-06-11 19:35     ` David VomLehn
2009-06-11 22:57     ` Grant Erickson
2009-06-12  0:33       ` David VomLehn
2009-06-12  5:33         ` Wolfgang Denk [this message]
2009-06-11 23:27   ` Mike Frysinger
2009-06-12  1:07     ` David VomLehn
2009-06-12  4:54       ` Robin Getz
2009-06-13 16:49         ` Jamie Lokier
2009-06-26 14:39   ` Robin Getz
2009-06-26 17:42     ` David VomLehn
2009-06-26 17:50       ` Mike Frysinger
2009-06-26 17:59       ` Robin Getz
2009-06-13 10:26 ` Russell King
2009-06-13 18:59   ` Wolfgang Denk
2009-06-14 18:33     ` Robin Getz

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=20090612053310.9E9D9832E416@gemini.denx.de \
    --to=wd@denx.de \
    --cc=dvomlehn@cisco.com \
    --cc=gerg@snapgear.com \
    --cc=gerickson@nuovations.com \
    --cc=hari@in.ibm.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=rmk@arm.linux.org.uk \
    --cc=tim.bird@am.sony.com \
    --cc=vapier@gentoo.org \
    /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).