public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com, dhinds@sonic.net
Subject: Re: [PATCH] reduce size of bridge regions for yenta.c
Date: Sat, 24 Aug 2002 19:18:26 +0200	[thread overview]
Message-ID: <3D67BFE2.6010403@colorfullife.com> (raw)
In-Reply-To: 3D67A042.5030706@colorfullife.com

dhinds pointed me to a recent thread with another possible workaround:

The ICH-3M bridge is actually a transparent bridge that forwards all 
memory IO:

<<<< ich-3M datasheet (29071601.pdf)

MEMBASE Memory Base Register (HUB-PCI D30:F0)
Offset Address: 20 21h Attribute: R/W
Default Value: FFF0h Size: 16 bits
This register defines the base of the hub interface to PCI 
non-prefetchable memory range. Since the ICH3 will forward all hub 
interface memory accesses to PCI, the ICH3 will only use this 
information for determining when not to accept cycles as a target. This 
register must be initialized by the configuration software. For the 
purpose of address decode, address bits A[19:0] are assumed to be 0. 
Thus, the bottom of the defined memory address range will be aligned to 
a 1-MB boundary.
<<<<

Perhaps a pci-quirk should set

	bus->resource[1] = bus->parent->resource[1];

for the ICH-3M.

No patch, I don't understand the pci layer good enough to write such a 
quirk.

But IMHO the changes to yenta.c should be applied anyway: allocating 8 
MB, without any fallback, without reasonable error output is gross.

--
	Manfred


      reply	other threads:[~2002-08-24 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-24 15:03 [PATCH] reduce size of bridge regions for yenta.c Manfred Spraul
2002-08-24 17:18 ` Manfred Spraul [this message]

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=3D67BFE2.6010403@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=dhinds@sonic.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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