From: James Bottomley <James.Bottomley@steeleye.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] proposed changes to dino.c
Date: 12 Dec 2003 09:58:48 -0500 [thread overview]
Message-ID: <1071241131.1814.5.camel@mulgrave> (raw)
In-Reply-To: <20031212074838.GA16885@colo.lackof.org>
On Fri, 2003-12-12 at 02:48, Grant Grundler wrote:
> I just realized some drivers may need to access data (not code)
> in the ROM. I'm not aware of any but I don't want to under
> estimate how creative people can get. Just something to beware
> when bringing up new cards.
Hmm, well, we can back it out if people start hitting problems.
The reason for it is the Quad tulip card: The bridge chip only requests
a 1MB PCI window, but each chip has two memory BARs: the iomem region
(128bytes, with page alignment) and the ROM (256Kb). The bridge
allocation routines seem to work the BARs in reverse, so by the time the
ROM BARs are allocated, the memory window is full and none of the
devices can function.
I suppose I could look at a two phase approach: count all the resources
and sizes and then resize the bridge window appropriately...we actually
already need to do this for the GSC window on my C360...firmware
allocates too much space in the GSC/8 window and I run out of iomem
space for devices on the GSC/10.
James
next prev parent reply other threads:[~2003-12-12 14:59 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 [this message]
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
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=1071241131.1814.5.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--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 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.