All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Lane <jingai@shell.faradic.net>
To: bh40@calva.net, jingai@shell.faradic.net
Cc: debian-powerpc@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: r128 driver still borked in XF4.0.1-9pre10
Date: Wed, 6 Dec 2000 20:07:54 -0500	[thread overview]
Message-ID: <200012070107.eB717sJ23539@shell.faradic.net> (raw)


> >  Bus  0, device  15, function  0:
> >    PCI bridge: DEC DC21052 (rev 1).
> >      Medium devsel.  Fast back-to-back capable.  Master Capable.
> >Latency=32.  Min Gnt=4.
>
> It's indeed a PCI<->PCI bridge. Please look at /proc/device-tree to see
> where the AAPL,interrupt is hidden for bus 1 (should be in the PCI<->PCI
> node).

Appears to be:

/proc/device-tree/bandit/pci-bridge/AAPL,interrupts

Thanks for the help
-j

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

             reply	other threads:[~2000-12-07  1:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-07  1:07 Jonathan Lane [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-07  0:02 r128 driver still borked in XF4.0.1-9pre10 Jonathan Lane

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=200012070107.eB717sJ23539@shell.faradic.net \
    --to=jingai@shell.faradic.net \
    --cc=bh40@calva.net \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@lists.linuxppc.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 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.