linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis <hollis-lists@austin.rr.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Matt Porter <mporter@mvista.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PReP and generic PCI resource assignment
Date: Wed, 8 Aug 2001 20:34:30 -0500	[thread overview]
Message-ID: <01080820343003.00492@silence.internal> (raw)
In-Reply-To: <20010808102731.24623@smtp.adsl.oleane.com>


On Wednesday 08 August 2001 05:27, Benjamin Herrenschmidt wrote:
> >The problem is that root in this case is the PCI memory resource of the
> > host bridge, which correctly starts at 0xc0000000... but NOT in bus
> > terms. In bus terms it starts at 0x0. (CPU physical 0xc0000000 = PCI bus
> > 0x0 [IO mem].) So the new resource is assigned 0xc1000000, which is
> > written back to the BAR with pcibios_update_resource... which is way
> > wrong.
>
> The resource is in CPU space. The problem must be with
> pcibios_update_resource, which is responsible for doing the proper
> offset. If you look closely, it substracts hose->pci_mem_offset from the
> resource before writing it to the BAR.
> If your hose pci_mem_offset is wrong, then it can't work. It should be
> 0xc0000000 on PReP.

Yes, it is. I misinterpretted my debug output... :/

At any rate, relocating PCI resource 1 on this controller from 0x0 to
0x01000000 causes my VGA console to go backwards endian. I don't know why
this would be the case... Re-moving it back to 0x0 fixes the symptom. Any
ideas on why this could happen? I think VGA is all IO, no memory at all?

I'm curious about PCIBIOS_MIN_MEM... Why does that exist, and why was it
given that value?

-Hollis

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-08-09  1:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08  5:11 PReP and generic PCI resource assignment Hollis
2001-08-08  5:43 ` ashish anand
2001-08-08 12:23   ` Benjamin Herrenschmidt
2001-08-08 10:27 ` Benjamin Herrenschmidt
2001-08-09  1:34   ` Hollis [this message]
2001-08-09 10:18     ` Benjamin Herrenschmidt
2001-08-09 16:14       ` Matt Porter
2001-08-10  8:38         ` Geert Uytterhoeven
2001-08-10  9:56           ` Benjamin Herrenschmidt
2001-08-10 10:51             ` Geert Uytterhoeven
2001-08-10 19:34           ` Hollis Blanchard
2001-08-11 17:43             ` Geert Uytterhoeven

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=01080820343003.00492@silence.internal \
    --to=hollis-lists@austin.rr.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mporter@mvista.com \
    /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;
as well as URLs for NNTP newsgroup(s).