From: Grant Grundler <grundler@parisc-linux.org>
To: Matthew Wilcox <willy@debian.org>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
PARISC list <parisc-linux@lists.parisc-linux.org>,
Grant Grundler <grundler@parisc-linux.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [parisc-linux] proposed changes to dino.c
Date: Sat, 13 Dec 2003 13:52:20 -0700 [thread overview]
Message-ID: <20031213205220.GA6089@colo.lackof.org> (raw)
In-Reply-To: <20031213203343.GP27116@parcelfarce.linux.theplanet.co.uk>
On Sat, Dec 13, 2003 at 08:33:43PM +0000, Matthew Wilcox wrote:
> Well, we could allocate more than 8MB for a Dino's PCI window. As I
> recall (should check the spec ...) we can set any of the 30 bits in
> the status register to forward any of those 8MB chunks to the PCI bus.
that's correct. Only the top most and bottom most bits are fixed
at zero (both 8MB ranges are not routeable).
> I think we could also get away with allocating less than 8MB to an
> individual PCI bus by programming the CCIO registers to not forward all
> that space to the parent GSC bus. But none of this has been necessay so
> far, and I hope we don't manage to concoct a situation where it might be.
"Doctor, when I stand like this, my neck hurts."
"Don't do that."
:^)
grant
next prev parent reply other threads:[~2003-12-13 20:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 4:37 [parisc-linux] proposed changes to dino.c James Bottomley
2003-12-10 4:54 ` Grant Grundler
2003-12-10 15:12 ` James Bottomley
2003-12-10 21:54 ` James Bottomley
2003-12-12 7:48 ` Grant Grundler
2003-12-12 11:30 ` Thomas Bogendoerfer
2003-12-12 15:00 ` James Bottomley
2003-12-12 15:38 ` Thomas Bogendoerfer
2003-12-12 14:58 ` James Bottomley
2003-12-12 19:28 ` Alan Cox
2003-12-13 3:51 ` Grant Grundler
2003-12-13 15:33 ` Alan Cox
2003-12-13 15:45 ` James Bottomley
2003-12-13 20:33 ` Matthew Wilcox
2003-12-13 20:52 ` Grant Grundler [this message]
2003-12-13 3:53 ` Grant Grundler
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=20031213205220.GA6089@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=James.Bottomley@steeleye.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.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 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.