-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dominik Brodowski wrote:
> As the "unsupported PCI PM cap regs version (1)" handling caused trouble on
> some devices, it got removed in 2.6.11-rc5.
hm, the only change in the changelog with "PCI_PM_CAP" is:
<[EMAIL PROTECTED]>
[PATCH] PCI:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dominik Brodowski wrote:
As the unsupported PCI PM cap regs version (1) handling caused trouble on
some devices, it got removed in 2.6.11-rc5.
hm, the only change in the changelog with PCI_PM_CAP is:
[EMAIL PROTECTED]
[PATCH] PCI: support
On Mon, Feb 28, 2005 at 01:31:03AM +0100, Christian Kujau wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> hi,
>
> i'm running 2.6.11-rc2-bk10 and still get my syslog clobbered with
> messages like this:
>
> PCI: :00:0c.0 has unsupported PM cap regs version (1)
>
> $ lspci |
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i'm running 2.6.11-rc2-bk10 and still get my syslog clobbered with
messages like this:
PCI: :00:0c.0 has unsupported PM cap regs version (1)
$ lspci | grep :00:0c.0
:00:0c.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i'm running 2.6.11-rc2-bk10 and still get my syslog clobbered with
messages like this:
PCI: :00:0c.0 has unsupported PM cap regs version (1)
$ lspci | grep :00:0c.0
:00:0c.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX
On Mon, Feb 28, 2005 at 01:31:03AM +0100, Christian Kujau wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i'm running 2.6.11-rc2-bk10 and still get my syslog clobbered with
messages like this:
PCI: :00:0c.0 has unsupported PM cap regs version (1)
$ lspci | grep
6 matches
Mail list logo