* Unsupported PM cap regs version 1
@ 2005-03-05 20:05 Lee Revell
2005-03-06 20:06 ` Dominik Brodowski
0 siblings, 1 reply; 2+ messages in thread
From: Lee Revell @ 2005-03-05 20:05 UTC (permalink / raw)
To: linux-kernel
Every time I load the driver for my SBLive Platinum I get this log
message:
PCI: 0000:00:0f.0 has unsupported PM cap regs version (1)
even though CONFIG_PM is not set.
I see that this issue came up in January on LKML but there was no
resolution.
First, why don't we support PM cap regs versions other than 2? Second,
why is this printk() necessary? If we really don't support older
versions for a good reason, do we really need to constantly remind the
user about it? Especially if power management is disabled?
The overall effect is to give the user the impression that the hardware
is somehow broken.
Lee
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Unsupported PM cap regs version 1
2005-03-05 20:05 Unsupported PM cap regs version 1 Lee Revell
@ 2005-03-06 20:06 ` Dominik Brodowski
0 siblings, 0 replies; 2+ messages in thread
From: Dominik Brodowski @ 2005-03-06 20:06 UTC (permalink / raw)
To: Lee Revell; +Cc: linux-kernel
On Sat, Mar 05, 2005 at 03:05:35PM -0500, Lee Revell wrote:
> Every time I load the driver for my SBLive Platinum I get this log
> message:
>
> PCI: 0000:00:0f.0 has unsupported PM cap regs version (1)
PM cap regs version 1 is handled in 2.6.11 yet again, the message should be
gone for this case by now.
> even though CONFIG_PM is not set.
PM caps are needed to activate devices, even if CONFIG_PM is not set.
Dominik
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-03-06 20:06 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-03-05 20:05 Unsupported PM cap regs version 1 Lee Revell
2005-03-06 20:06 ` Dominik Brodowski
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).