linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: geert@linux-m68k.org
Cc: grant@borg.umn.edu, mmporter@home.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: Grabbing an Interrupt for a Brain-dead PCI Device
Date: Thu, 9 Mar 2000 07:58:03 +0100 (CET)	[thread overview]
Message-ID: <200003090658.HAA00456@piglet.grunz.lu> (raw)
In-Reply-To: <Pine.LNX.4.05.10003082011320.8208-100000@callisto.of.borg>


On   8 Mar, this message from Geert Uytterhoeven echoed through cyberspace:
>> Also, regarding memory address space resources, is there a routine I can
>> call that says "Assign this card some resource space because it hasn't
>> been assigned one yet"?
>
> Yes there is, somewhere in drivers/pci/. I don't know yet whether it works.

I doubt it will work on a PowerMac; see what the resource 'checking'
code finds as parent resources (r is a mem resource, pr is its parent
resource):

Mar  9 07:24:29 piglet kernel:    Resources: r.start=f2000400, r.end=f200043f,
pr.start=00000000, pr.end=ffffffff.

As far as I can tell, parent resource would be the memory region held
by the parent bridge, out of which this region was allocated. A bit
huge, this region, isn't it?

Then again, Apple's host bridges might not conform entirely to the PCI
spec in the way they advertise their resources available for
assignment...

Those with the PCI spec at hand out there, is there such a thing as
resource registers in bridges (be it P2P or host) that inform about
what is available to devices behind this particular bridge?

Maybe there's another job for the fixup code...

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-03-09  6:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-05 21:30 HELP: Power Mac G3 PCI Strangeness in 2.2 and 2.3 Grant Erickson
2000-03-06 11:04 ` Geert Uytterhoeven
2000-03-07 20:40   ` Grabbing an Interrupt for a Brain-dead PCI Device Grant Erickson
2000-03-07 21:00     ` Geert Uytterhoeven
2000-03-07 22:00     ` Michel Lanners
2000-03-08  8:31       ` Geert Uytterhoeven
2000-03-08 14:15         ` Matt Porter
2000-03-08 18:47       ` Grant Erickson
2000-03-08 19:12         ` Geert Uytterhoeven
2000-03-09  6:58           ` Michel Lanners [this message]
2000-03-09 12:52             ` Gabriel Paubert

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=200003090658.HAA00456@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=geert@linux-m68k.org \
    --cc=grant@borg.umn.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mmporter@home.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 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).