From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/7] 83xx: Migrate CONFIG_DDR_ECC_CMD toCONFIG_EDAC_FSL_ECC
Date: Mon, 09 Nov 2009 19:09:48 -0600 [thread overview]
Message-ID: <1257815388.10661.40.camel@localhost.localdomain> (raw)
In-Reply-To: <D7CCA83BB0796C49BC0BB53B6AB1208979FE01@zch01exm21.fsl.freescale.net>
Please stop top-posting.
On Tue, 2009-11-10 at 08:51 +0800, Liu Dave-R63238 wrote:
> 83xx ECC test code is really perfect, but it is regretful that it can
> not reused to 85xx/86xx right now.
> I'm not sure which approach is better between Peter's and this.
> Because I still have not read carefully Peter's code.
<snip>
The 83xx ECC test code may have been perfect for your needs, but it was
not perfect for mine:) Or most people I would think. As I mentioned
before, I put an emphasis on the error reporting. Wolfgang and I
discussed exactly this in v1 of the patch:
http://www.mail-archive.com/u-boot at lists.denx.de/msg24216.html
<quote>
> 83xx, 85xx, and 86xx could all share an implementation I believe. I
> didn't integrate the 83xx in this patch because it seemed to have a
> different "goal" than the patch I submitted. The 83xx implementation
> supported a high degree of tweaking registers which I personally find
> unnecessary for general use. I think that if someone wants that level
> of control, they could just modify the registers directly since they
> have to have the 83xx user's manual handy anyway.
Agreed.
> The implementation I submitted has limited, common features and much
> better error reporting. The error reporting is the feature that would
> be used 98% of the time, not the tweaking of registers. I'd be happy to
> include the 83xx implementation in this patch, but I'd vote to strip out
> most of the current 83xx features - ie basically remove the 83xx ecc
> code and replace it with the 85/86xx implementation I submitted. Would
> 83xx people be OK with this? Or have any suggestions on what the
> combined implementation should look like?
I have yet to see a user who actually uses the existing code on 83xx,
so as far as I am concerned I'll be fine with the common, simpler
code.
</quote>
Best,
Peter
next prev parent reply other threads:[~2009-11-10 1:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 23:37 [U-Boot] [PATCH v2 0/7] 83xx/85xx/86xx ECC update Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 1/7] 83xx: Add CCSR DDR register offsets Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 2/7] 85xx/86xx: Add ECC error injection defines Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 3/7] 83xx/85xx/86xx: Add ECC support Peter Tyser
2009-11-10 0:25 ` Liu Dave-R63238
2009-11-10 0:32 ` Peter Tyser
2009-11-10 0:38 ` Liu Dave-R63238
2009-11-10 0:42 ` Liu Dave-R63238
2009-11-10 0:46 ` Liu Dave-R63238
2009-11-10 1:01 ` Peter Tyser
2009-11-10 1:08 ` Liu Dave-R63238
2009-11-10 1:20 ` Peter Tyser
2009-11-10 2:15 ` Ira W. Snyder
2009-11-10 3:07 ` Peter Tyser
2009-11-10 16:51 ` Ira W. Snyder
2009-11-10 17:36 ` Peter Tyser
2009-11-10 17:53 ` Ira W. Snyder
2009-11-09 23:37 ` [U-Boot] [PATCH 4/7] 83xx: Migrate CONFIG_DDR_ECC_CMD to CONFIG_EDAC_FSL_ECC Peter Tyser
2009-11-10 0:51 ` [U-Boot] [PATCH 4/7] 83xx: Migrate CONFIG_DDR_ECC_CMD toCONFIG_EDAC_FSL_ECC Liu Dave-R63238
2009-11-10 1:09 ` Peter Tyser [this message]
2009-11-09 23:37 ` [U-Boot] [PATCH 5/7] Add check for ECC errors during SDRAM POST and mtest Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 6/7] xes: Add 8xxx post support Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 7/7] xes: Enable memory POST and ECC error reporting Peter Tyser
2009-12-16 15:55 ` [U-Boot] [PATCH v2 0/7] 83xx/85xx/86xx ECC update Peter Tyser
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=1257815388.10661.40.camel@localhost.localdomain \
--to=ptyser@xes-inc.com \
--cc=u-boot@lists.denx.de \
/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.