public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
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 11:13:20 +0200	[thread overview]
Message-ID: <200907081113.20158.sr@denx.de> (raw)
In-Reply-To: <7562912cc29928bc1eb0ab343fcf22b1b01e0245.1246398582.git.ptyser@xes-inc.com>

Hi Peter,

this patch breaks some PPC4xx boards. Those enabling CONFIG_DDR_ECC, e.g. 
canyonlands:

[stefan at stefan-desktop u-boot-ppc4xx (master)]$ ./MAKEALL canyonlands
Configuring for canyonlands board...
fsl_dma.c:50:2: error: #error "Freescale DMA engine not supported on your 
processor"
make[1]: *** No rule to make target `.depend', needed by `libdma.a'.  Stop.


On Wednesday 01 July 2009 00:15:51 Peter Tyser wrote:

<snip>

> +++ b/include/asm-ppc/config.h
> @@ -30,8 +30,9 @@
>  #endif
>
>  #ifndef CONFIG_FSL_DMA
> -#if defined(CONFIG_DDR_ECC) && !defined(CONFIG_ECC_INIT_VIA_DDRCONTROLLER)
> && \ -	(defined(CONFIG_MPC85xx) || defined(CONFIG_MPC86xx))
> +#if ((!defined CONFIG_MPC83xx && defined(CONFIG_DDR_ECC) &&	\
> +	!defined(CONFIG_ECC_INIT_VIA_DDRCONTROLLER)) ||		\
> +	(defined(CONFIG_MPC83xx) && defined(CONFIG_DDR_ECC_INIT_VIA_DMA)))
>  #define CONFIG_FSL_DMA
>  #endif
>  #endif

The #if construct doesn't seem to work for all PPC boards. I have to admit 
that I don't understand the logic enabling the CONFIG_FSL_DMA define. It would 
be great if you (or somebody else with the FSL insight) could fix this.

Thanks.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  parent reply	other threads:[~2009-07-08  9:13 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 [this message]
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
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=200907081113.20158.sr@denx.de \
    --to=sr@denx.de \
    --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