From: Philippe De Muyter <phdm@macqel.be>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: ARCH=ppc -> ARCH=powerpc : help needed for dts file
Date: Mon, 3 Mar 2008 22:26:22 +0100 [thread overview]
Message-ID: <20080303212622.GB20382@netgate.macqel> (raw)
In-Reply-To: <47CC696C.4090103@freescale.com>
Hi Scott,
On Mon, Mar 03, 2008 at 03:11:08PM -0600, Scott Wood wrote:
> Philippe De Muyter wrote:
>> Is the PCI-interrupt map that part of the dts file :
>> interrupt-map = <
>> /* IDSEL 0x02 */
>> 1000 0 0 1 &mpic 1 1
>> 1000 0 0 2 &mpic 2 1
>> 1000 0 0 3 &mpic 3 1
>> 1000 0 0 4 &mpic 4 1
>> /* IDSEL 0x03 */
>> 1800 0 0 1 &mpic 4 1
>> 1800 0 0 2 &mpic 1 1
>> 1800 0 0 3 &mpic 2 1
>> 1800 0 0 4 &mpic 3 1
>> ...
>
> Yes.
>
>> I do not understand anything there :(
>
> It maps PCI interrupts to mpic interrupts. The first three cells are the
> PCI address (only the device number is unmasked), then the PCI interrupt
> (INTA=1, INTB=2, etc.), then a phandle to the parent interrupt controller,
> then the interrupt specifier for the parent controller.
Thanks
The following seems important also :
/*
interrupts = <18 2>;
*/
/* interrupts number are coded in hexa ! */
interrupts = <12 2 19 2 1a 2 1b 2 35 2 36 2 37 2>;
I have replaced the interrupts spec in comments by the longer interrupts spec
below, and it seems to have some positive effect, but I do not know
precisely what I have described there.
I know that 25, 26, 27, 53, 54 and 55 decimal i(hence 19, 1a etc...) are the
interrupts numbers that I had in the ARCH=ppc version. I added 18 because
of the error message, but it did not help.
What should be described here and how ?
Philippe
next prev parent reply other threads:[~2008-03-03 21:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 14:47 ARCH=ppc -> ARCH=powerpc : help needed for dts file Philippe De Muyter
2008-03-03 14:54 ` Grant Likely
2008-03-03 17:07 ` Scott Wood
2008-03-03 21:05 ` Philippe De Muyter
2008-03-03 21:11 ` Scott Wood
2008-03-03 21:26 ` Philippe De Muyter [this message]
2008-03-03 21:41 ` Benjamin Herrenschmidt
2008-03-04 8:19 ` Philippe De Muyter
2008-03-03 21:55 ` Scott Wood
2008-03-04 8:08 ` Philippe De Muyter
2008-03-04 8:22 ` Benjamin Herrenschmidt
2008-03-04 9:10 ` Philippe De Muyter
2008-03-05 4:52 ` David Gibson
2008-03-05 5:01 ` Benjamin Herrenschmidt
2008-03-05 16:15 ` Philippe De Muyter
2008-03-05 20:14 ` Benjamin Herrenschmidt
2008-03-05 23:34 ` Philippe De Muyter
2008-03-05 16:32 ` Scott Wood
2008-03-05 23:46 ` Benjamin Herrenschmidt
2008-03-07 0:10 ` Philippe De Muyter
2008-03-07 0:19 ` Benjamin Herrenschmidt
2008-03-09 22:31 ` Philippe De Muyter
2008-03-09 22:36 ` Benjamin Herrenschmidt
2008-03-11 0:32 ` David Gibson
2008-03-11 11:46 ` Philippe De Muyter
2008-03-11 22:42 ` David Gibson
2008-05-06 22:54 ` Andy Fleming
2008-05-07 7:50 ` Philippe De Muyter
2008-05-07 7:54 ` Stephen Rothwell
2008-03-03 21:26 ` Benjamin Herrenschmidt
2008-03-04 8:34 ` Philippe De Muyter
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=20080303212622.GB20382@netgate.macqel \
--to=phdm@macqel.be \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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.