From: Grant Grundler <grundler@parisc-linux.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] proposed changes to dino.c
Date: Tue, 9 Dec 2003 21:54:29 -0700 [thread overview]
Message-ID: <20031210045429.GA18782@colo.lackof.org> (raw)
In-Reply-To: <1071031038.1977.1.camel@mulgrave>
On Tue, Dec 09, 2003 at 11:37:16PM -0500, James Bottomley wrote:
> This updates dino to configure unassigned resources (primarily so I can
> get it to recognise my yenta cardbus bridge).
James and I talked about this offline. Issue was card-mode dino
and the PCI yenta bridge were colliding on the bus numbering.
The card-mode Dino bus numbering was assuming no PCI-PCI bridges
for *all* the host bridges, not just the card-mode bridges.
I expect a combination of 4-port tulip and card-mode dinoe would
have exposed this problem too.
> The side effect is that it will reorder all the resources in the dino
> window.
I think this will be ok as long firmware doesn't try to remember
and PCI resources. STI is what I don't know about and worry a bit.
Otherwise the diff looks good to me. I trust it works for you
and hopefully a few other people can try it too. If not, we
can always fix it more later...
thanks,
grant
next prev parent reply other threads:[~2003-12-10 4:54 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 [this message]
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
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=20031210045429.GA18782@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=James.Bottomley@steeleye.com \
--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