public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Richard Henderson <rth@twiddle.net>,
	axp-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: PCI-PCI bridges mess in 2.4.x
Date: Wed, 08 Nov 2000 17:43:54 -0500	[thread overview]
Message-ID: <3A09D72A.C2730D0@mandrakesoft.com> (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> <20001108142513.A5244@jurassic.park.msu.ru> <20001108093744.D27324@twiddle.net> <20001109010336.A1367@jurassic.park.msu.ru>

Ivan Kokshaysky wrote:
> But actually I'm concerned that all this code doesn't work at all -
> see reports from Michal Jaegermann (the bridge acts as if it drops
> config space transactions randomly). I have a lot of suggestions, but
> it's a pain to debug something without access to real hardware - just
> a waste of the precious time of everyone who is involved...
> So I would probably wait a week or two until I'll have something with
> bridges :-(

FWIW, I just tested rth's update of your path on my x86 SMP box, and a
laptop with two CardBus bridges (two CardBus slots).  Both worked
fine...

I am still worried that the conditions which generate the following
message indicate a problem still exists.  (this message exists w/out
your patch..)
Unknown bridge resource 0: assuming transparent

	Jeff


-- 
Jeff Garzik             | "When I do this, my computer freezes."
Building 1024           |          -user
MandrakeSoft            | "Don't do that."
                        |          -level 1
-
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/

  reply	other threads:[~2000-11-08 22:44 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 [this message]
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
     [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=3A09D72A.C2730D0@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=axp-list@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rth@twiddle.net \
    /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