From: Richard Henderson <rth@twiddle.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
axp-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: PCI-PCI bridges mess in 2.4.x
Date: Wed, 8 Nov 2000 09:20:46 -0800 [thread overview]
Message-ID: <20001108092046.A27324@twiddle.net> (raw)
In-Reply-To: <20001101153420.A2823@jurassic.park.msu.ru> <20001101093319.A18144@twiddle.net> <20001103111647.A8079@jurassic.park.msu.ru> <20001103011640.A20494@twiddle.net> <20001106192930.A837@jurassic.park.msu.ru> <20001108013931.A26972@twiddle.net> <3A0977A7.53641C52@mandrakesoft.com>
In-Reply-To: <3A0977A7.53641C52@mandrakesoft.com>
On Wed, Nov 08, 2000 at 10:56:23AM -0500, Jeff Garzik wrote:
> Setting bit 1 in dev->resource[x].start, below, seems incorrect. Should
> you be programming the PCI BAR directly, instead?
No, that's the reason this is a quirk. The hardware is already
only responding to one and only one address. The old code did
exactly the same thing, only not inside the quirk framework,
which made it kinda harder to figure out what was going on.
> I wonder about this code:
>
> > + /* ??? Reserve some resources for CardBus */
> > + if (dev->class >> 8 == PCI_CLASS_BRIDGE_CARDBUS) {
> > + io_reserved += 8*1024;
> > + mem_reserved += 32*1024*1024;
> > + continue;
> > + }
Got a better suggestion? It does seem completely reasonable to
reserve some address space for a CardBus bridge if we find one.
r~
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-08 17:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001101153420.A2823@jurassic.park.msu.ru>
[not found] ` <20001101093319.A18144@twiddle.net>
[not found] ` <20001103111647.A8079@jurassic.park.msu.ru>
[not found] ` <20001103011640.A20494@twiddle.net>
[not found] ` <20001106192930.A837@jurassic.park.msu.ru>
2000-11-08 9:39 ` PCI-PCI bridges mess in 2.4.x Richard Henderson
2000-11-08 10:19 ` Sean Hunter
2000-11-08 11:25 ` Ivan Kokshaysky
2000-11-08 17:37 ` Richard Henderson
2000-11-08 22:03 ` Ivan Kokshaysky
2000-11-08 22:43 ` Jeff Garzik
2000-11-08 23:49 ` Richard Henderson
2000-11-09 14:41 ` Ivan Kokshaysky
2000-11-08 23:48 ` Richard Henderson
2000-11-09 14:39 ` Ivan Kokshaysky
2000-11-09 20:37 ` Gérard Roudier
2000-11-09 23:17 ` Ivan Kokshaysky
2000-11-10 18:35 ` Gérard Roudier
2000-11-10 21:29 ` Ivan Kokshaysky
2000-11-10 21:26 ` Gérard Roudier
2000-11-08 15:56 ` Jeff Garzik
2000-11-08 17:20 ` Richard Henderson [this message]
[not found] ` <20001108113859.A10997@animx.eu.org>
[not found] ` <3A098594.A85DFE0D@mandrakesoft.com>
[not found] ` <20001108122306.A11107@animx.eu.org>
[not found] ` <3A0989CC.2537FCEA@mandrakesoft.com>
2000-11-09 16:33 ` Wakko Warner
2000-11-09 23:31 ` Michal Jaegermann
2000-11-10 10:52 ` Sean Hunter
2000-11-08 18:22 Dunlap, Randy
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 16:36 Wakko Warner
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=20001108092046.A27324@twiddle.net \
--to=rth@twiddle.net \
--cc=axp-list@redhat.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.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