From: Yoichi Yuasa <yuasa@linux-mips.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: yuasa@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Reverting old hack
Date: Wed, 24 Feb 2010 09:03:33 +0900 [thread overview]
Message-ID: <20100224090333.44a16d0a.yuasa@linux-mips.org> (raw)
In-Reply-To: <201002231601.15136.bjorn.helgaas@hp.com>
On Tue, 23 Feb 2010 16:01:14 -0700
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Monday 22 February 2010 06:28:30 am Ralf Baechle wrote:
> > It's a while since I last looked into this but here's how things afair
> > are working on a MIPS-based Cobalt system.
> >
> > The system is based on a MIPS processor and a GT-64111 system controller.
> > Addresses within a certain CPU address range are passed to the PCI bus as
> > I/O cycles without address cycles. Since memory is starting at CPU address
> > zero (and has to because of the processors used), that address window has
> > to get mapped somewhere else. So a CPU access to some virtual address gets
> > translated to physical address 0xf00001f0. The GT-64111 passes this to the
> > PCI bus as I/O port address 0xf00001f0. Finally the VT82C586 chip which
> > only decodes the low 16 bits drops treats this as an I/O port space address
> > 0x1f0.
>
> Yoichi, can you try the patch below? I think this is basically the
> approach Ben suggested long ago:
> http://marc.info/?l=linux-kernel&m=119733290624544&w=2
It works fine with 2.6.34 queue tree.
pci.c change is already committed by Ralf.
Thanks,
Yoichi
next prev parent reply other threads:[~2010-02-24 0:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 11:31 Reverting old hack Ralf Baechle
2010-02-20 12:18 ` Yoichi Yuasa
2010-02-20 14:57 ` Bjorn Helgaas
2010-02-21 7:45 ` Yoichi Yuasa
2010-02-22 20:55 ` Bjorn Helgaas
2010-02-22 23:51 ` Yoichi Yuasa
2010-02-23 0:15 ` Bjorn Helgaas
2010-02-23 0:50 ` Yoichi Yuasa
2010-02-21 2:57 ` Bjorn Helgaas
2010-02-22 0:09 ` Bjorn Helgaas
2010-02-22 5:07 ` Bjorn Helgaas
2010-02-22 6:39 ` Yoichi Yuasa
2010-02-22 13:28 ` Ralf Baechle
2010-02-23 23:01 ` Bjorn Helgaas
2010-02-24 0:03 ` Yoichi Yuasa [this message]
2010-02-24 16:41 ` Ralf Baechle
2010-02-24 16:59 ` Bjorn Helgaas
2010-02-24 17:41 ` Ralf Baechle
2010-02-24 20:53 ` Benjamin Herrenschmidt
2010-02-25 8:39 ` Yoichi Yuasa
2010-02-25 14:29 ` Ralf Baechle
2010-02-24 16:13 ` Ralf Baechle
2010-02-24 16:23 ` Bjorn Helgaas
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=20100224090333.44a16d0a.yuasa@linux-mips.org \
--to=yuasa@linux-mips.org \
--cc=benh@kernel.crashing.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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