From: David Woodhouse <dwmw2@infradead.org>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: CeLinux <celinux-dev@tree.celinuxforum.org>,
Linux Embedded <linux-embedded@vger.kernel.org>
Subject: Re: How to store kernel pranic/oops
Date: Mon, 28 Dec 2009 12:12:34 +0000 [thread overview]
Message-ID: <1262002354.3181.411.camel@macbook.infradead.org> (raw)
In-Reply-To: <4B3899DB.1020308@gmail.com>
On Mon, 2009-12-28 at 12:43 +0100, Marco Stornelli wrote:
> It would be nice to have a "ramoops" to save in a circular buffer in a
> persistent ram this kind of information. Any comments? Is there already
> anything similar out-of-tree?
Can't it be done with what's in the tree already? Just create an MTD
device using phram or something else, then point mtdoops at it.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
prev parent reply other threads:[~2009-12-28 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 11:43 How to store kernel pranic/oops Marco Stornelli
2009-12-28 12:12 ` David Woodhouse [this message]
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=1262002354.3181.411.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=linux-embedded@vger.kernel.org \
--cc=marco.stornelli@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).