Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S129611AbRBMRND>; Tue, 13 Feb 2001 12:13:03 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S130017AbRBMRMx>; Tue, 13 Feb 2001 12:12:53 -0500
Received: from mandrakesoft.mandrakesoft.com ([216.71.84.35]:27696 "EHLO
	mandrakesoft.mandrakesoft.com") by vger.kernel.org with ESMTP
	id <S129611AbRBMRMm>; Tue, 13 Feb 2001 12:12:42 -0500
Date: Tue, 13 Feb 2001 11:11:56 -0600 (CST)
From: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>
To: Tim Wright <timw@splhi.com>
cc: Adam Lackorzynski <al10@inf.tu-dresden.de>,
        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
In-Reply-To: <20010213085830.B7226@kochanski.internal.splhi.com>
Message-ID: <Pine.LNX.3.96.1010213111120.24228B-100000@mandrakesoft.mandrakesoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 13 Feb 2001, Tim Wright wrote:
> 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.

We can get tech info on ServerWorks...  just ask specific questions, and
hardware contacts etc. will do the rest.

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/