From: Andreas Bombe <andreas.bombe@munich.netsurf.de>
To: "Maxim S. Shatskih" <maxim@storagecraft.com>
Cc: Albrecht Dreß <ad@mpifr-bonn.mpg.de>,
FireWire devel <linux1394-devel@eclipt.uni-klu.ac.at>,
LinuxPPC-Dev Liste <linuxppc-dev@lists.linuxppc.org>
Subject: Re: FireWire + Apple PB G3: some success
Date: Thu, 24 Feb 2000 17:17:16 +0100 [thread overview]
Message-ID: <20000224171715.B2137@storm.local> (raw)
In-Reply-To: <002801bf7e71$24c2e5a0$0100000a@sauron>; from maxim@storagecraft.com on Thu, Feb 24, 2000 at 05:44:53AM +0300
On Thu, Feb 24, 2000 at 05:44:53AM +0300, Maxim S. Shatskih wrote:
> > It's not seen because the driver is stuck in bus reset. The most
> > probable reason is that DMA is not working. I can't think of a reason
> > right now (since it does work on another PPC).
>
> I've had this problem on NT4. Are you sure that the DMA enable bit in PCI
> config space is set?
To quote Albert's patch:
+ pci_read_config_word (dev, PCI_COMMAND, &w);
+ pci_write_config_word (dev, PCI_COMMAND, w | PCI_COMMAND_MASTER | PCI_COMMAND_MEMORY | PCI_COMMAND_IO);
He sets the PCI master flag (which should be the only thing disabling /
enabling DMA in general). In the standard sources pci_set_master() is
used, which does the same.
Setting PCI_COMMAND_IO on the other hand is unneccessary since the
PCILynx only uses memory mapped I/O (if I understand PCI config
correctly). I don't know if this flag is harmful if there are no I/O
ports.
--
Andreas E. Bombe <andreas.bombe@munich.netsurf.de>
http://home.pages.de/~andreas.bombe/ DSA key 0x04880A44
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-24 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-23 10:24 FireWire + Apple PB G3: some success Albrecht Dre_
2000-02-23 23:58 ` Andreas Bombe
2000-02-24 2:44 ` [Linux1394-devel] " Maxim S. Shatskih
2000-02-24 16:17 ` Andreas Bombe [this message]
2000-02-28 12:59 ` Albrecht Dre_
2000-02-28 19:02 ` Andreas Bombe
2000-02-29 16:07 ` Ryuichi Oikawa
2000-02-29 16:45 ` Benjamin Herrenschmidt
2000-03-02 17:22 ` Ryuichi Oikawa
2000-03-01 7:30 ` Albrecht Dre_
-- strict thread matches above, loose matches on Subject: below --
2000-03-03 10:07 Benjamin Herrenschmidt
2000-03-03 19:46 Dan Bethe
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=20000224171715.B2137@storm.local \
--to=andreas.bombe@munich.netsurf.de \
--cc=ad@mpifr-bonn.mpg.de \
--cc=linux1394-devel@eclipt.uni-klu.ac.at \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=maxim@storagecraft.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.