From: Ralf Baechle <ralf@linux-mips.org>
To: Peter Horton <phorton@bitbox.co.uk>
Cc: Alan <alan@lxorguk.ukuu.org.uk>,
Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH] [MIPS] Fixed PCI resource fixup
Date: Mon, 22 Jan 2007 20:35:17 +0000 [thread overview]
Message-ID: <20070122203517.GA26801@linux-mips.org> (raw)
In-Reply-To: <45AB839A.50003@bitbox.co.uk>
On Mon, Jan 15, 2007 at 01:37:30PM +0000, Peter Horton wrote:
Time to get this going again ...
> I've just checked on the Qube2 here and the RTC can be found at
> 0x1000.0070, 0x1001.0070 etc so the VIA bridge is only decoding the low
> 16 address lines for I/O space. Handy really otherwise it wouldn't work
> with the GT-64111 :-)
Thanks, that's what I was expecting. So to resume the discussion about
how to fix this I suggest:
o Set cobalt_io_resource to the 0x10001000 - 0x10010000 range.
o Set ioport_resource to the 0x10000000 - 0x10010000 range.
o set mips_io_port_base to 0xa0000000
o set cobalt_pci_controller.io_offset back to 0
And then since we're not longer cheating about the true value of the
port addresses on the PCI bus used, add 0x10000000 to all of the start
and end values in cobalt_io_resources.
Does that sound reasonable?
Ralf
next prev parent reply other threads:[~2007-01-22 20:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 5:55 [PATCH] [MIPS] Fixed PCI resource fixup Yoichi Yuasa
2007-01-11 14:31 ` Ralf Baechle
2007-01-11 14:47 ` Yoichi Yuasa
2007-01-11 15:45 ` Atsushi Nemoto
2007-01-12 2:46 ` Yoichi Yuasa
2007-01-12 13:54 ` Atsushi Nemoto
2007-01-13 15:20 ` Yoichi Yuasa
2007-01-12 14:16 ` Peter Horton
2007-01-12 14:40 ` Alan
2007-01-12 14:49 ` Alan
[not found] ` <20070114115539.GA5755@linux-mips.org>
2007-01-15 13:37 ` Peter Horton
2007-01-22 20:35 ` Ralf Baechle [this message]
2007-01-23 1:35 ` Yoichi Yuasa
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=20070122203517.GA26801@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@linux-mips.org \
--cc=phorton@bitbox.co.uk \
--cc=yoichi_yuasa@tripeaks.co.jp \
/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