In article <[EMAIL PROTECTED]>,
Martin Mares <[EMAIL PROTECTED]> wrote:
>
>What leads you to your belief it's correct? The lspci dump Adam has sent
>to the list shows that there's something utterly wrong with our understanding
>of the ServerWorks config registers -- they seem to say that the prim
On Thu, 8 Feb 2001, Adam Lackorzynski wrote:
> On Thu Feb 08, 2001 at 03:06:27 -0800, Andre Hedrick wrote:
> > Have you got a hack for 2.2.18/19x ??
>
> I do not have problems with 2.2.x Kernels here. They see all the PCI
> devices just fine.
But it will not register the device
Bus 0, devic
>
> What leads you to your belief it's correct? The lspci dump Adam has sent
> to the list shows that there's something utterly wrong with our
understanding
> of the ServerWorks config registers -- they seem to say that the primary
> bus numbers are 00 and 01, but in reality they are 00 and 02.
On Thu Feb 08, 2001 at 03:06:27 -0800, Andre Hedrick wrote:
> Have you got a hack for 2.2.18/19x ??
I do not have problems with 2.2.x Kernels here. They see all the PCI
devices just fine.
Adam
--
Adam [EMAIL PROTECTED]
Lackorzynski http://a.home.dhs.org
-
To unsubscri
Dan,
Have you got a hack for 2.2.18/19x ??
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court
Hello!
> The ServerWorks peer bus problem is still present on the 2.4.1 kernel. The
> problem stems from the fact that there can be more than one secondary bus
> for a given north bridge. For example, the Compaq Proliant DL580 has two
> "root busses" coming off of a single north bridge. I'm in
The ServerWorks peer bus problem is still present on the 2.4.1 kernel. The
problem stems from the fact that there can be more than one secondary bus
for a given north bridge. For example, the Compaq Proliant DL580 has two
"root busses" coming off of a single north bridge. I'm including below an
7 matches
Mail list logo
