From: Ralf Baechle <ralf@linux-mips.org>
To: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>
Cc: linux-mips@linux-mips.org
Subject: Re: pci-ip27 memory ranges
Date: Sat, 24 Apr 2004 20:21:46 +0200 [thread overview]
Message-ID: <20040424182146.GD26165@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10404241059030.18252-100000@helios.et.put.poznan.pl>
On Sat, Apr 24, 2004 at 11:00:44AM +0200, Stanislaw Skowronek wrote:
> Why does the pci-ip27 driver register all memory resources (0UL - ~0UL)? I
> had to change it to the appropriate Xtalk window to get the kernel to
> recognize PCI at all.
The IP27 PCI code as it is in CVS is incomplete or even broken - however
fixing isn't entirely trivial. The current workaround which I use - and
which due to being just an evil hack is not in CVS - to only scan the PCI
code. The problem is the firmware does a very simple setup which hurts
performance very badly, so eventually Linux will have to do a full PCI
configuration for all PCI busses.
> Now, the IOC3 makes a kernel panic. Will see...
Ralf
prev parent reply other threads:[~2004-04-24 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 9:00 pci-ip27 memory ranges Stanislaw Skowronek
2004-04-24 10:30 ` Christoph Hellwig
2004-04-24 18:21 ` Ralf Baechle [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=20040424182146.GD26165@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=sskowron@ET.PUT.Poznan.PL \
/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