From: Tim Wright <timw@splhi.com>
To: Adam Lackorzynski <al10@inf.tu-dresden.de>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
linux-kernel@vger.kernel.org, Dan.Zink@compaq.com
Subject: Re: PCI bridge handling 2.4.0-test10 -> 2.4.2-pre3
Date: Tue, 13 Feb 2001 08:58:30 -0800 [thread overview]
Message-ID: <20010213085830.B7226@kochanski.internal.splhi.com> (raw)
In-Reply-To: <20010212140419.A11619@lug-owl.de> <20010213003815.A17962@inf.tu-dresden.de> <20010213122013.A31590@lug-owl.de> <20010213154137.A19612@inf.tu-dresden.de>
In-Reply-To: <20010213154137.A19612@inf.tu-dresden.de>; from al10@inf.tu-dresden.de on Tue, Feb 13, 2001 at 03:41:37PM +0100
I believe that, in general, we want working fixup routines so the we don't
have to rely on the BIOS. That said, it's apparent that the ServerWorks
routines are broken. Fixing them is going to be troublesome, given ServerWorks
attitude towards releasing specs. It's on my list of things to try to sort out,
since some of the Netfinities I use are ServerWorks based.
Tim
On Tue, Feb 13, 2001 at 03:41:37PM +0100, Adam Lackorzynski wrote:
> On Tue Feb 13, 2001 at 12:20:14 +0100, Jan-Benedict Glaw wrote:
> > On Tue, Feb 13, 2001 at 12:38:15AM +0100, Adam Lackorzynski wrote:
> > > On Mon Feb 12, 2001 at 14:04:20 +0100, Jan-Benedict Glaw wrote:
> > > > I've got a "Bull Express5800/Series" (dual P3) with a DAC1164 RAID
> > > > controller. The mainboard is ServerWorks based and however, 2.4.2-pre3
> > > > fails to find the RAID controller. I think there's a problem at
> > > > scanning PCI busses behind PCI bridges. Here's the PCI bus layout as
> > > > 2.4.0-test10 recognizes it:
> > >
> > > --- pci-pc.c.orig Tue Feb 13 00:02:50 2001
> > > +++ pci-pc.c Tue Feb 13 00:19:29 2001
> > > @@ -953,9 +953,6 @@
> > [Removal of serverworks fixup routines]
> >
> > That patch cured the problem; the box is up'n'running again. Thanks!
>
> Ok, fine.
>
> Since this patch works for Jan, Dan and me I'd suggest putting it into
> the kernel and thus removing the fixup routines (Anyone know the reason
> why they're there?).
>
> Comments?!
>
>
> Adam
> --
> Adam al10@inf.tu-dresden.de
> Lackorzynski http://a.home.dhs.org
--
Tim Wright - timw@splhi.com or timw@aracnet.com or twright@us.ibm.com
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI
next prev parent reply other threads:[~2001-02-13 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 13:04 Jan-Benedict Glaw
2001-02-12 23:38 ` Adam Lackorzynski
2001-02-13 11:20 ` Jan-Benedict Glaw
2001-02-13 14:41 ` Adam Lackorzynski
2001-02-13 16:58 ` Tim Wright [this message]
2001-02-13 17:11 ` Jeff Garzik
2001-02-13 17:30 Zink, Dan
2001-02-14 6:27 ` Jeff Garzik
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=20010213085830.B7226@kochanski.internal.splhi.com \
--to=timw@splhi.com \
--cc=Dan.Zink@compaq.com \
--cc=al10@inf.tu-dresden.de \
--cc=jbglaw@lug-owl.de \
--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
all inboxes | Powered by JetHome®