From: Mark Takatz <takatz@pericle.com>
To: linuxppc-dev@ozlabs.org
Subject: use generic pci_assign_unassign_resources
Date: Fri, 13 Mar 2009 16:42:15 -0600 [thread overview]
Message-ID: <49BAE147.4060102@pericle.com> (raw)
Ben,
We're looking at the fixes you put in place for the various PCI errors
and we think this is the solution we need for our system, a GE Fanuc CM6
PPC board (single 8641), but your patches appear to apply either to
2.6.24 or 2.6.25, and we have 2.6.23. Do you know of any similar work
done on the 2.6.23 release?
Thanks in advance for any help you can provide,
--
Mark J. Takatz
Pericle Communications Company
1910 Vindicator Drive, Suite 100
Colorado Springs, CO 80919
Office: (719) 548-1170
Cell: (719) 287-5267
Fax: (719) 548-1211
takatz@pericle.com
next reply other threads:[~2009-03-13 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 22:42 Mark Takatz [this message]
2009-03-15 23:56 ` use generic pci_assign_unassign_resources Benjamin Herrenschmidt
2009-03-16 14:40 ` Mark Takatz
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=49BAE147.4060102@pericle.com \
--to=takatz@pericle.com \
--cc=linuxppc-dev@ozlabs.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).