On Tue, 13 Feb 2001, Zink, Dan wrote:
> Does it make sense to try and keep up with the latest and greatest in
> chipsets
> when there is a hardware independent way of doing things? You may be able
> to
> get information on current chipsets, but every time something changes, the
> kernel may be
reason for the
BIOS's existence.
Dan
-Original Message-
From: Jeff Garzik [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 13, 2001 11:12 AM
To: Tim Wright
Cc: Adam Lackorzynski; Jan-Benedict Glaw; [EMAIL PROTECTED];
Zink, Dan
Subject: Re: PCI bridge handling 2.4.0-test10 -> 2.4.2-p
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
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
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
On Tue, Feb 13, 2001 at 12:38:15AM +0100, Adam Lackorzynski wrote:
Hi Adam!
> 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
> >
On Tue, Feb 13, 2001 at 12:38:15AM +0100, Adam Lackorzynski wrote:
Hi Adam!
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
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
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
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
reason for the
BIOS's existence.
Dan
-Original Message-
From: Jeff Garzik [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 13, 2001 11:12 AM
To: Tim Wright
Cc: Adam Lackorzynski; Jan-Benedict Glaw; [EMAIL PROTECTED];
Zink, Dan
Subject: Re: PCI bridge handling 2.4.0-test10 - 2.4.2-pre3
On Tue, 13 Feb 2001, Zink, Dan wrote:
Does it make sense to try and keep up with the latest and greatest in
chipsets
when there is a hardware independent way of doing things? You may be able
to
get information on current chipsets, but every time something changes, the
kernel may be broken
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
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
14 matches
Mail list logo
