From: Yuasa Yoichi <yuasa@linux-mips.org>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>
Subject: Re: [PATCH v2] char drivers: Ram oops/panic logger
Date: Wed, 10 Mar 2010 18:20:33 +0900 [thread overview]
Message-ID: <21eaeb5a1003100120x6cd3f69ak598954af3c9fe955@mail.gmail.com> (raw)
In-Reply-To: <2ea1731b1003100002w104633ffy1ae46ef3d245e5b5@mail.gmail.com>
2010/3/10 Marco Stornelli <marco.stornelli@gmail.com>:
> 2010/3/10 Yuasa Yoichi <yuasa@linux-mips.org>:
>> Hi,
>>
>> 2010/3/10 Marco Stornelli <marco.stornelli@gmail.com>:
>>> Ramoops, like mtdoops, can log oops/panic information but in RAM.
>>
>> What is different from mtdoops + mtd-ram?
>>
>> Yoichi
>>
>
> It can be used in a very easy way with persistent RAM for systems
> without flash support. For this systems, with this driver, it's no
> more needed add to the kernel the mtd subsystem with advantage in
> footprint as I said in the description.
right.
But,
> In addition, you can save
> flash space and store this information only in RAM. I think it's very
> useful for embedded systems.
CONFIG_MTD_RAM uses only RAM.
I think there's no big difference about this point.
Yoichi
next prev parent reply other threads:[~2010-03-10 9:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 17:41 [PATCH v2] char drivers: Ram oops/panic logger Marco Stornelli
2010-03-10 2:08 ` Yuasa Yoichi
2010-03-10 8:02 ` Marco Stornelli
2010-03-10 9:20 ` Yuasa Yoichi [this message]
2010-03-10 12:15 ` Marco Stornelli
2010-03-12 22:48 ` Andrew Morton
2010-03-12 23:31 ` Jamie Lokier
2010-03-13 8:49 ` Marco Stornelli
2010-03-15 3:09 ` Jamie Lokier
2010-03-15 8:11 ` Marco Stornelli
2010-03-13 8:50 ` Marco Stornelli
2010-03-13 14:50 ` Geert Uytterhoeven
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=21eaeb5a1003100120x6cd3f69ak598954af3c9fe955@mail.gmail.com \
--to=yuasa@linux-mips.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@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).