public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI updates - 32-bit IO support
Date: Thu, 20 Dec 2001 09:37:10 +0000	[thread overview]
Message-ID: <20011220093710.C29925@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20011218235024.N13126@flint.arm.linux.org.uk> <9vrmea$mef$1@cesium.transmeta.com> <20011219.213019.35013739.davem@redhat.com>
In-Reply-To: <20011219.213019.35013739.davem@redhat.com>; from davem@redhat.com on Wed, Dec 19, 2001 at 09:30:19PM -0800

On Wed, Dec 19, 2001 at 09:30:19PM -0800, David S. Miller wrote:
> Don't the PCI specs actually talk about 24-bits in fact?
> 
> Russell does you box really have the full 32-bits or is it
> really just 24-bits?

Shrug - the chip documentation isn't good enough to indicate either.

What I do know is:

- setting the bridge and eepro100 up with 16-bit IO addresses causes PCI
  master aborts.
- setting the bridge and eepro100 up with 32-bit IO addresses which
  correspond to the host MMIO region, it works perfectly.

It appears that the first bridge converts the mmio access into a PCI
IO read/write cycle without any address translation.  So, when I
access mmio 0x90011000, it would appear to cause a PCI IO cycle at
the same address.

The MMIO region for this bus is 0x90010000 - 0x9001ffff, so its impossible
to test the effect of different upper 16-bits.

I suppose I could waste some time by getting Linux to generate lots of IO
cycles and scoping the PCI bus lines to find the PCI address, but I think
its rather academic in light of the above.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  parent reply	other threads:[~2001-12-20  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 23:50 [PATCH] PCI updates - 32-bit IO support Russell King
2001-12-20  3:37 ` H. Peter Anvin
2001-12-20  5:30   ` David S. Miller
2001-12-20  5:57     ` H. Peter Anvin
2001-12-20  9:37     ` Russell King [this message]
2001-12-20 13:18       ` Ivan Kokshaysky

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=20011220093710.C29925@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=davem@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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