From: Peter Horton <phorton@bitbox.co.uk>
To: Ralf Baechle <ralf@linux-mips.org>
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, 15 Jan 2007 13:37:30 +0000 [thread overview]
Message-ID: <45AB839A.50003@bitbox.co.uk> (raw)
In-Reply-To: <20070114115539.GA5755@linux-mips.org>
Ralf Baechle wrote:
> On Fri, Jan 12, 2007 at 02:49:05PM +0000, Alan wrote:
>
>>>> The GT-64111 passes the CPU addresses straight onto the PCI bus and does
>>>> not remove the offset of the Galileo's PCI window in CPU space. This
>>>> means the only PCI I/O addresses that can be supported are 0x1000.0000
>>>> to 0x11ff.ffff, hence the negative 'io_offset'.
>> Does this mean it can't hit PCI I/O space legacy addresses (0x1F0 etc) ?
>>
>> If so can you set CONFIG_NO_ATA_LEGACY in your platform configuration
>
> In the meantime I checked this against the Galileo documentation. Which
> says just like Yoichi and Peter that the GT-64111 is passing local
> addresses in the configured PCI memory or I/O windows straight through to
> the PCI bus. Reconfiguring the PCI I/O window to start at physical address
> zero is not really an option because the CPU has it's exception vectors
> there.
>
> There is one inconsistency in the whole story still. Cobalts use a PC-style
> legacy RTC chip at I/O port 0x70 and that seems to work just fine. I suspect
> the the VIA Apollo SuperIO chip makes this work by just dropping some of the
> high I/O port address bits ...
>
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 :-)
P.
next prev parent reply other threads:[~2007-01-15 13:37 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 [this message]
2007-01-22 20:35 ` Ralf Baechle
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=45AB839A.50003@bitbox.co.uk \
--to=phorton@bitbox.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.