linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Albrecht Dreß <ad@mpifr-bonn.mpg.de>,
	LinuxPPC-Dev Liste <linuxppc-dev@lists.linuxppc.org>
Subject: Re: FireWire on Apple PowerBook PISMO
Date: Thu, 11 May 2000 14:54:21 +0200	[thread overview]
Message-ID: <20000511125422.13794@mailhost.mipsys.com> (raw)
In-Reply-To: <3912AE0C.9C8D096B@mpifr-bonn.mpg.de>


On Fri, May 5, 2000, Albrecht Dreß <ad@mpifr-bonn.mpg.de> wrote:

>With the information from some people on the LinuxPPC list, I was able
to talk
>to the FireWire OHCI controller in the new Apple PowerBook (PISMO).  I had to
>add the vendor/device id of the chip and (as usual, as OpenFirmware does
>not do
>it) add a few lines to enable the pci device.  The "basic" startup seems to
>work, but any further operation (e.g. testlibraw) hangs.  Maybe one of the FW
>gurus can tell me from the logs below what is missing?

OF does it, but will undo it when "quiesce" is called (like for the USB
controllers). This is a safety to make sure the chip is no longer bus
mastering when the OS relocates itself.

A strange thing is that the address 0xf5000000 looks more like an IO
region than a memory region, but this may not be a problem actually. (the
cell is inside the north bridge which has a weird PCI management.

It's possible that, like the GMAC ethernet (which is also inside Apple
ASIC), the device clock need to be enabled in the memory controller. You
can try to look at OF methods for it to see what's up.


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

      reply	other threads:[~2000-05-11 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-05 11:18 FireWire on Apple PowerBook PISMO Albrecht Dre_
2000-05-11 12:54 ` Benjamin Herrenschmidt [this message]

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=20000511125422.13794@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=ad@mpifr-bonn.mpg.de \
    --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 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).