linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andre Schwarz <andre.schwarz@matrix-vision.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-ppc list <linuxppc-dev@ozlabs.org>
Subject: Re: simple MPC5200B system
Date: Tue, 18 Mar 2008 16:14:35 +0100	[thread overview]
Message-ID: <47DFDC5B.90304@matrix-vision.de> (raw)
In-Reply-To: <fa686aa40803180731g3892e737h29db0cb917946588@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2186 bytes --]

Grant Likely schrieb:
> On Tue, Mar 18, 2008 at 4:34 AM, Andre Schwarz
> <andre.schwarz@matrix-vision.de> wrote:
>   
>>  Grant,
>>
>>  sorry for having troubled you. Looks like the build system has been in an
>> invalid state...
>>
>>  After doing a git-pull and "make distclean" + "make mpc5200_defconfig" the
>> system is finally up and running.
>>     
>
> Heh; I hate it when that happens.  :-)
>
> Congratulations.
>
> g.
>
>
>   
Grant,

this leads to the next questions ... :-)

I've read some discussions about the "interrupt-map" attribute of the 
pci node. I tried to follow Ben and David in their explanations - 
obviously I didn't really get it.
Looks like there are a lot of people outside who need some enlightenment 
... including me, of course.

Maybe you can clarify this ?

Taken from motionpro.dts ...

    interrupt-map = <c000 0 0 1 &mpc5200_pic 0 0 3 // 1st slot
                                 c000 0 0 2 &mpc5200_pic 1 1 3
                                 c000 0 0 3 &mpc5200_pic 1 2 3
                                 c000 0 0 4 &mpc5200_pic 1 3 3

                                 c800 0 0 1 &mpc5200_pic 1 1 3 // 2nd slot
                                 c800 0 0 2 &mpc5200_pic 1 2 3
                                 c800 0 0 3 &mpc5200_pic 1 3 3
                                 c800 0 0 4 &mpc5200_pic 0 0 3>;


First parameter seems to be the slot number, i.e. IDSEL line of the PCI 
device.
How is this value coded ? Are these the bits 15..11 of the configuration 
address ?

2nd + 3rd paramter : no clue ! can you explain ?

4th : seem to be INT_A ... _D of a PCI device. Usually a device uses 
only INT_A. Do we need 4 entries in any case ?

5th : ok - parent pic

6th ... 8th  : IRQ representation of the parent pic, which gives :

    6th : 0=CRIT for irq0 pin, 1=MAIN for irq1..3 pins
    7th : irq number. 1 for the irq0 pin inside CRIT level. irq1..3 have 
number 1..3 inside MAIN level.
    8th : should be 3 = "level low" which is default for PCI.




regards,
Andre


MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweiler  - Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschäftsführer: Gerhard Thullner, Werner Armingeon, Uwe Furtner

[-- Attachment #2: Type: text/html, Size: 4089 bytes --]

  reply	other threads:[~2008-03-18 15:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16 19:15 simple MPC5200B system André Schwarz
2008-03-16 20:01 ` Grant Likely
2008-03-17  9:35   ` André Schwarz
2008-03-18  8:49   ` Andre Schwarz
2008-03-18 10:34     ` Andre Schwarz
2008-03-18 14:31       ` Grant Likely
2008-03-18 15:14         ` Andre Schwarz [this message]
2008-03-18 16:21           ` Grant Likely
2008-03-18 16:44             ` Andre Schwarz
2008-03-20  0:14     ` Wolfgang Denk
2008-03-20  0:21       ` David Gibson
2008-03-20  7:48         ` André Schwarz
2008-03-20  8:20           ` David Gibson
2008-03-20  9:11             ` André Schwarz
2008-03-20  9:29             ` Stefan Roese

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=47DFDC5B.90304@matrix-vision.de \
    --to=andre.schwarz@matrix-vision.de \
    --cc=grant.likely@secretlab.ca \
    --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).