From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/3] ARM: Add default system.h and uncompress.h
Date: Thu, 28 Jul 2011 08:21:23 -0500 [thread overview]
Message-ID: <4E316253.1070601@gmail.com> (raw)
In-Reply-To: <20110728095221.GA31473@n2100.arm.linux.org.uk>
On 07/28/2011 04:52 AM, Russell King - ARM Linux wrote:
> On Wed, Jul 27, 2011 at 10:32:11PM -0500, Rob Herring wrote:
>> One downside is you lose print capability in the decompressor. However,
>> I don't think the complexity that adds is worth the 1 line print.
>
> You're wrong there - it's very very useful to have that from the
> decompressor. It's saved many people (including us) a lot of wasted
> time caused by faulty hardware implementation.
>
> Normally, if the design of the SDRAM connections is poor, the first
> thing which catches it is the decompressor, and so its that which we
> really want error information from.
>
Agreed. I have seen that case as well, but generally only very early on
in board/chip bringup. Really, bootloaders need a decent memory test or
ability to load one.
> So no, losing that ability is not an option. Really.
If a platform has an uncompress.h, then you don't lose anything. Is it
something that has to *always* be available? Are you opposed to a config
option here? It can be available only for single arch/machine builds
similar to DEBUG_LL.
Rob
next prev parent reply other threads:[~2011-07-28 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 3:32 [RFC PATCH 0/3] ARM: Add default system.h and uncompress.h Rob Herring
2011-07-28 3:32 ` [RFC PATCH 1/3] ARM: include mach headers before common arm headers Rob Herring
2011-07-28 3:32 ` [RFC PATCH 2/3] ARM: add a default mach/uncompress.h header Rob Herring
2011-07-28 3:32 ` [RFC PATCH 3/3] ARM: add a default mach/system.h header Rob Herring
2011-07-28 4:40 ` [RFC PATCH 0/3] ARM: Add default system.h and uncompress.h Nicolas Pitre
2011-07-28 13:53 ` Rob Herring
2011-07-28 9:52 ` Russell King - ARM Linux
2011-07-28 13:21 ` Rob Herring [this message]
2011-07-28 15:01 ` Russell King - ARM Linux
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=4E316253.1070601@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).