Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: 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 20:33:43 +0000	[thread overview]
Message-ID: <20031213203343.GP27116@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1071330357.2024.4.camel@mulgrave>

On Sat, Dec 13, 2003 at 10:45:54AM -0500, James Bottomley wrote:
> Hmm, yes...I completely blow away the ROM bar in the patch...what I
> should do is just to remove it's IORESOURCE_MEM flag so it isn't
> ordinarily allocated (but it's requested location and size are still
> available).  Then any driver that wanted access could get it...we still
> have 1020kB available for mapping up to three roms in the bridge window.

I rather think the generic PCI code should be fixed to not enable the
ROM resource by default.  Many PCI devices do not cope well with this
*anyway*, we definitely shouldn't be doing it in anything except the
driver.

> The alternative is just to resize the bridge window after we've counted
> the resources...I'm less enthusiastic about this beacuse the dino PCI
> window has a maximum size of 8MB for everything on the bus...plug a few
> of these four ports into a dino PCI bus and we'll still run out of
> memory.

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.
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.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2003-12-13 20:33 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 [this message]
2003-12-13 20:52                   ` Grant Grundler
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=20031213203343.GP27116@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.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