From: Ira Snyder <iws@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 12/12] 83xx: Add support for fsl_dma driver
Date: Wed, 8 Jul 2009 08:24:51 -0700 [thread overview]
Message-ID: <20090708152451.GA14979@ovro.caltech.edu> (raw)
In-Reply-To: <1247063401.11207.183.camel@localhost.localdomain>
On Wed, Jul 08, 2009 at 09:30:01AM -0500, Peter Tyser wrote:
> On Wed, 2009-07-08 at 09:07 -0500, Kumar Gala wrote:
> > Peter,
> >
> > Also, I'm not seeing anyone defining CONFIG_DDR_ECC_INIT_VIA_DMA for
> > 83xx. I don't see any reason not to use DMA on 83xx.
>
> When I submitted the original patch I didn't see any 83xx boards using
> either CONFIG_ECC_INIT_VIA_DDRCONTROLLER or CONFIG_DDR_ECC_INIT_VIA_DMA.
> It didn't look like the 83xx platform supported the
> CONFIG_ECC_INIT_VIA_DDRCONTROLLER option at all, although some 83xx
> boards make reference to !CONFIG_DDR_ECC_INIT_VIA_DMA.
>
> I don't have any 83xx boards to test on and am not that familiar with
> the 83xx so I didn't look into fixing the inconsistencies. In a perfect
> world CONFIG_ECC_INIT_VIA_DDRCONTROLLER would be enabled for all 83xx
> cpus that supported it, and the DMA init would be the default.
>
> I'd be happy to send a patch to change the 83xx arch to use DMA to
> initialize ECC when !CONFIG_ECC_INIT_VIA_DDRCONTROLLER if someone else
> will test. Do all 83xx CPUs have the Elo DMA controller DMA engine?
>
I'm always happy to test anything on an mpc8349emds.
I don't have any ECC RAM for my mpc8349emds board, but I do have a
custom 8349ea-based board with ECC RAM. The U-Boot port is just a
trimmed down copy of the mpc8349emds port, so I can test with that.
Ira
next prev parent reply other threads:[~2009-07-08 15:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 22:15 [U-Boot] [PATCH v2 00/12] 8xxx dma updates Peter Tyser
2009-06-30 22:15 ` [U-Boot] [PATCH v2 01/12] 85xx, 86xx: Break out DMA code to a common file Peter Tyser
2009-07-02 4:04 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 02/12] fsl_dma: Add bitfield definitions for common registers Peter Tyser
2009-07-02 4:04 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 03/12] fsl_dma: Use proper I/O access functions Peter Tyser
2009-07-02 4:04 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 04/12] fsl_dma: Add support for arbitrarily large transfers Peter Tyser
2009-07-02 4:07 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 05/12] fsl_dma: Fix Channel Start bug in dma_check() Peter Tyser
2009-07-02 4:08 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 06/12] 8xxx: Rename dma_xfer() to dmacpy() Peter Tyser
2009-07-02 4:08 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 07/12] fsl_dma: Move dma function prototypes to common header file Peter Tyser
2009-07-02 4:13 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 08/12] 85xx, 86xx: Move dma_init() call to common code Peter Tyser
2009-07-02 4:13 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 09/12] fsl_dma: Break out common memory initialization function Peter Tyser
2009-07-02 4:13 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 10/12] fsl_dma: Make DMA transactions snoopable Peter Tyser
2009-07-02 4:13 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 11/12] 83xx: Replace CONFIG_ECC_INIT_VIA_DDRC references Peter Tyser
2009-07-02 4:12 ` Kumar Gala
2009-07-02 15:25 ` Kim Phillips
2009-07-02 16:17 ` Kumar Gala
2009-06-30 22:15 ` [U-Boot] [PATCH v2 12/12] 83xx: Add support for fsl_dma driver Peter Tyser
2009-07-02 16:17 ` Kumar Gala
2009-07-08 9:13 ` Stefan Roese
2009-07-08 14:07 ` Kumar Gala
2009-07-08 14:30 ` Peter Tyser
2009-07-08 14:36 ` Kumar Gala
2009-07-08 15:24 ` Ira Snyder [this message]
2009-07-08 14:13 ` 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=20090708152451.GA14979@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox