From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ethan Benson <erbenson@alaska.net>
Cc: yaboot-users@lists.penguinppc.org,
yaboot-devel@lists.penguinppc.org,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>,
Linux/PPC-devel <linuxppc-dev@lists.linuxppc.org>,
yellowdog-general@lists.terrasoftsolutions.com,
yellowdog-devel@lists.terrasoftsolutions.com,
g5-test@lists.terrasoftsolutions.com
Subject: Re: [YABOOT] Preliminary ofpath with 2.6 kernel support NEEDS TESTING
Date: Mon, 22 Mar 2004 14:07:31 +1100 [thread overview]
Message-ID: <1079924850.912.171.camel@gaston> (raw)
In-Reply-To: <20040322023536.GB21226@plato.local.lan>
On Mon, 2004-03-22 at 13:35, Ethan Benson wrote:
> * You must have 2.6.4 or newer, previous versions lack necessary sysfs
> information.
Isn't 2.6.3 enough ?
> * You must have sysfs mounted (normally on /sys, but ofpath should be
> able to detect where its mounted).
>
> * You must still have /proc/ide so if this becomes a configurable
> option like /proc/scsi you must have it enabled (/proc/scsi is also
> required for machines with SATA drives).
Note that if you are using a G5 with DART enabled (that is with more
than 2Gb of RAM), you _MUST_ apply the following patch, or access to
the /proc/scsi/sata_svw entry will break the driver:
diff -Nru a/arch/ppc64/kernel/pmac_iommu.c b/arch/ppc64/kernel/pmac_iommu.c
--- a/arch/ppc64/kernel/pmac_iommu.c Tue Mar 16 08:10:33 2004
+++ b/arch/ppc64/kernel/pmac_iommu.c Tue Mar 16 08:10:33 2004
@@ -289,8 +289,11 @@
* things simple. Setup all PCI devices to point to this table
*/
while ((dev = pci_find_device(PCI_ANY_ID, PCI_ANY_ID, dev)) != NULL) {
- dn = PCI_GET_DN(dev);
-
+ /* We must use pci_device_to_OF_node() to make sure that
+ * we get the real "final" pointer to the device in the
+ * pci_dev sysdata and not the temporary PHB one
+ */
+ struct device_node *dn = pci_device_to_OF_node(dev);
if (dn)
dn->iommu_table = &iommu_table_pmac;
}
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-22 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 2:35 [YABOOT] Preliminary ofpath with 2.6 kernel support NEEDS TESTING Ethan Benson
2004-03-22 3:07 ` Benjamin Herrenschmidt [this message]
2004-03-23 4:55 ` digger vermont
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=1079924850.912.171.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=erbenson@alaska.net \
--cc=g5-test@lists.terrasoftsolutions.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=yaboot-devel@lists.penguinppc.org \
--cc=yaboot-users@lists.penguinppc.org \
--cc=yellowdog-devel@lists.terrasoftsolutions.com \
--cc=yellowdog-general@lists.terrasoftsolutions.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).