From: Alan <alan@lxorguk.ukuu.org.uk>
To: Peter Horton <phorton@bitbox.co.uk>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: [PATCH] [MIPS] Fixed PCI resource fixup
Date: Fri, 12 Jan 2007 14:40:42 +0000 [thread overview]
Message-ID: <20070112144042.74c4edca@localhost.localdomain> (raw)
In-Reply-To: <45A79847.1060302@bitbox.co.uk>
On Fri, 12 Jan 2007 14:16:39 +0000
Peter Horton <phorton@bitbox.co.uk> wrote:
> Ralf Baechle wrote:
> > On Thu, Jan 11, 2007 at 02:55:58PM +0900, Yoichi Yuasa wrote:
> >
> >> This patch has fixed IDE resources problem about Cobalt.
> >>
> >> pcibios_fixup_device_resources() changes non-movable resources.
> >> It cannot be changed if there is IORESOURCE_PCI_FIXED in the resource flags.
> >
> > <Ralf> anemo: Have you seen Yoichi's patch?
> > <anemo> Ralf: yes, but I could not see why ... My impression is IORESOURCE_PCI_FIXED and io_offset adjustment is irrerevant.
> > <Ralf> This whole fixup thing is really meant to handle machines where there is an offset between PCI bus addresses and CPU physical addresses.
> > <Ralf> And that exists regardless of IORESOURCE_PCI_FIXED
> > <anemo> I thought so too. So I can not see why youichi's patch fix something.
> > <Ralf> This may be the explanation:
> > <Ralf> static struct pci_controller cobalt_pci_controller = {
> > <Ralf> .pci_ops = >64111_pci_ops,
> > <Ralf> .mem_resource = &cobalt_mem_resource,
> > <Ralf> .mem_offset = 0,
> > <Ralf> .io_resource = &cobalt_io_resource,
> > <Ralf> .io_offset = 0 - GT_DEF_PCI0_IO_BASE,
> > <Ralf> };
> > <Ralf> I think he should have io_offset = 0.
> >
> > Which is what other GT-64120 platforms are using, so I wonder why that is
> > different on Cobalt.
> >
>
> 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'.
>
> I assume the GT-64120 remaps the PCI addresses somehow to remove the offset.
>
> P.
--
--
Sick of rip off UK rail fares ? Learn how to get far cheaper fares
http://zeniv.linux.org.uk/~alan/GTR/
next prev parent reply other threads:[~2007-01-12 14:29 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 [this message]
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
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=20070112144042.74c4edca@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-mips@linux-mips.org \
--cc=phorton@bitbox.co.uk \
--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.