lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:  <slrnej3egk.2kc.olecom@flower.upol.cz>
Date:	Sun, 15 Oct 2006 04:27:05 +0000 (UTC)
From:	Oleg Verych <olecom@...wer.upol.cz>
To:	linux-kernel@...r.kernel.org
Subject:  Re: sky2 (was Re: 2.6.18-mm2)

On 2006-10-09, Oleg Verych wrote:
> On 2006-10-09, Stephen Hemminger wrote:
>> On Sun, 08 Oct 2006 20:31:36 +0200
>> Matthias Hentges <oe@...tges.net> wrote:
>>
>>> 
>>> Oops, I forgot the "x" in lspci -vvvx, new dumps are attached.
>>
>>
>> I think I know what the problem is. The PCI access routines to access pci express
>> registers (ie reg > 256), only work if using MMCONFIG access. For some reason
>> your configuration doesn't want to use/allow that.
>
> In case you didn't read, here's top of thread about MMCONFIG 4 days ago:
><http://article.gmane.org/gmane.linux.ports.x86-64.general/1794>
>
> In short: due to Intel BIOS bug, mmconfig doesn't used in kernel.
> And kernel developers mainly do not care much (yet) about drivers, until
> vi$ta certified hardware will be in run.
> ____

[and, due to my dumb, not copied here Stephen's answer was:]

> Then I would argue that PCI express support is broken in the kernel.

____

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ