From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: sky2 (was Re: 2.6.18-mm2)
Date: Sun, 15 Oct 2006 04:27:05 +0000 (UTC) [thread overview]
Message-ID: <slrnej3egk.2kc.olecom@flower.upol.cz> (raw)
In-Reply-To: <slrneilm0q.3mc.olecom@deen.upol.cz.local>
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@hentges.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.
____
next prev parent reply other threads:[~2006-10-15 4:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060928155053.7d8567ae.akpm@osdl.org>
2006-09-28 23:07 ` Jeff Garzik
2006-09-28 23:19 ` Stephen Hemminger
2006-09-30 0:26 ` Matthias Hentges
2006-10-04 2:57 ` Matthias Hentges
2006-10-04 3:26 ` Stephen Hemminger
2006-10-07 19:48 ` Matthias Hentges
2006-10-08 13:41 ` Matthias Hentges
2006-10-08 16:20 ` Stephen Hemminger
2006-10-08 17:00 ` Matthias Hentges
2006-10-08 18:31 ` Matthias Hentges
2006-10-09 16:45 ` Stephen Hemminger
2006-10-09 23:14 ` Oleg Verych
2006-10-15 4:27 ` Oleg Verych [this message]
2006-10-10 10:45 ` Matthias Hentges
2006-10-10 0:02 ` Beber
2006-09-28 23:25 ` Andrew Morton
2006-09-28 23:30 ` Stephen Hemminger
2006-09-29 16:04 ` Andrea Gelmini
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=slrnej3egk.2kc.olecom@flower.upol.cz \
--to=olecom@flower.upol.cz \
--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®