From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Subject: Current linuxppc_2_4_devel breakage
Date: Tue, 13 Nov 01 13:45:01 PST [thread overview]
Message-ID: <0111132145.AA21341@ivan.Harhan.ORG> (raw)
Hi there,
Current linuxppc_2_4_devel is broken on the Adirondack and I presume a bunch of
other platforms. After making it compile again (after the cpuinfo change), I
found that it dies as soon as it tries to perform a PCI config cycle in
find_bridges. Now this is after it has called setup_indirect_pci() to tell it
how to make these cycles. On the Adirondack I don't currently use a static
mapping for the CPC710 registers, and when I call setup_indirect_pci I pass it
physical addresses. setup_indirect_pci does its own ioremaps on both addresses
(CONFIG_ADDR and CONFIG_DATA), and it always worked before. It doesn't work
right now, however. Hacking the port to map the CPC710 registers virtual=
physical with io_block_mapping() in my ppc_md.setup_io_mappings() makes it
work, so I know the problem is there.
MS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-11-13 21:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0111132145.AA21341@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.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 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).