linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Giuseppe Coviello <cjg@cruxppc.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Sam440ep support
Date: Tue, 20 May 2008 07:50:28 -0500	[thread overview]
Message-ID: <20080520075028.0b286c73@zod.rchland.ibm.com> (raw)
In-Reply-To: <1211210447.11958.10.camel@marquez.cjg.home>

On Mon, 19 May 2008 17:20:47 +0200
Giuseppe Coviello <cjg@cruxppc.org> wrote:


> +			usb@ef601000 {
> +				compatible = "ohci-be";
> +				reg = <ef601000 80>;
> +				interrupts = <8 4 9 4>;
> +				interrupt-parent = < &UIC1 >;

Are you sure the trigger/level settings on those interrupts is
correct?

> +			};	
> +		};
> +
> +		PCI0: pci@ec000000 {
> +			device_type = "pci";
> +			#interrupt-cells = <1>;
> +			#size-cells = <2>;
> +			#address-cells = <3>;
> +			compatible = "ibm,plb440ep-pci", "ibm,plb-pci";
> +			primary;
> +			reg = <0 eec00000 8	/* Config space access */
> +			       0 eed00000 4	/* IACK */
> +			       0 eed00000 4	/* Special cycle */
> +			       0 ef400000 40>;	/* Internal registers */
> +
> +			/* Outbound ranges, one memory and one IO,
> +			 * later cannot be changed. Chip supports a second
> +			 * IO range but we don't use it for now
> +			 */
> +			ranges = <02000000 0 a0000000 0 a0000000 0 20000000
> +				  01000000 0 00000000 0 e8000000 0 00010000>;
> +
> +			/* Inbound 2GB range starting at 0 */
> +			dma-ranges = <42000000 0 0 0 0 0 80000000>;

You have no interrupt mapping for the PCI node.  How do you have
working PCI here?

josh

  reply	other threads:[~2008-05-20 12:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 18:23 [PATCH] Sam440ep support Giuseppe Coviello
2008-05-05 18:27 ` Kumar Gala
2008-05-05 19:50   ` Gerhard Pircher
2008-05-05 23:44     ` Benjamin Herrenschmidt
2008-05-06  7:51       ` Gerhard Pircher
2008-05-06  8:48         ` Benjamin Herrenschmidt
2008-05-06  9:16           ` Gerhard Pircher
2008-05-06 10:12             ` Benjamin Herrenschmidt
2008-05-06 11:14               ` Takashi Iwai
2008-05-06 11:25                 ` Benjamin Herrenschmidt
2008-05-06 11:27                   ` Benjamin Herrenschmidt
2008-05-06 11:31                   ` Takashi Iwai
2008-05-06 11:34                     ` Benjamin Herrenschmidt
2008-05-14 12:26             ` ALSA fixes for non-coherent archs (Re: [PATCH] Sam440ep support) Takashi Iwai
2008-05-14 12:50               ` Gerhard Pircher
2008-05-14 21:01               ` Gerhard Pircher
2008-05-15  5:42                 ` Takashi Iwai
2008-05-19 17:23               ` Giuseppe Coviello
2008-05-20 12:48                 ` Takashi Iwai
2008-05-05 23:38   ` [PATCH] Sam440ep support Benjamin Herrenschmidt
2008-05-05 18:54 ` Josh Boyer
2008-05-05 23:40   ` Benjamin Herrenschmidt
2008-05-06  0:09     ` Josh Boyer
2008-05-05 23:36 ` Benjamin Herrenschmidt
2008-05-06  4:18   ` Sean MacLennan
2008-05-06 16:37 ` Giuseppe Coviello
2008-05-09 15:53   ` Giuseppe Coviello
2008-05-09 20:26     ` Josh Boyer
2008-05-19 12:47   ` Josh Boyer
2008-05-19 15:20     ` Giuseppe Coviello
2008-05-20 12:50       ` Josh Boyer [this message]
2008-05-20 13:34         ` Josh Boyer
2008-05-22 17:51           ` Giuseppe Coviello

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=20080520075028.0b286c73@zod.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=cjg@cruxppc.org \
    --cc=linuxppc-dev@ozlabs.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).