public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Ed Sweetman <safemode@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pci unsupported PM regs version (7), means hardware isn't working?
Date: Thu, 15 Dec 2005 04:25:36 -0500	[thread overview]
Message-ID: <20051215092536.GA8122@neo.rr.com> (raw)
In-Reply-To: <438F800C.1050903@comcast.net>

On Thu, Dec 01, 2005 at 05:58:20PM -0500, Ed Sweetman wrote:
> I'm getting this warning when i try to load the madwifi drivers on my 
> WRAP board for the WMIA-166AG mini-pci card using kernel 2.6.13.3 and 
> the latest trunk of madwifi.  
> 
> This is the only error that's printed before the HAL driver for madwifi 
> responds with "no hardware found or unsupported hardware" etc etc.   I 
> had to add the pcid's to madwifi for it to even detect it enough to try 
> and send it to the HAL module, but the madwifi dev team isn't looking at 
> any bug reports because of this printk that's being made by the PCI 
> subsystem in the kernel. 
> 
> So, does this printk mean anything (i've seen posts where the hardware 
> producing it was working, the printks were just a nuissance) or does it 
> indicate some issue the PCI subsystem is having in powering the card up 
> and communicating with it.   In either case, I'd be more than happy with 
> providing anyone able to patch the pci code with information i have on 
> the card. 
> 
> If it's nothing but a harmless warning, i'll forward the response to the 
> madwifi wiki and mailing list, so something can be done upstream to the 
> hal module to work the card. 
> 
> Thanks in advance. 

The power management spec version reported by the driver doesn't exist as
far as I know.  Would it be possible to see the output of "lspci -xxx"?

Even if the kernel isn't able to understand the PM registers, we may want
to assume the device is in D0 and print a warning. The bar restore changes
possibly have changed this behavior.  As a result, pci_enable_device() would
return an error.

Thanks,
Adam

      reply	other threads:[~2005-12-15  8:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01 22:58 pci unsupported PM regs version (7), means hardware isn't working? Ed Sweetman
2005-12-15  9:25 ` Adam Belay [this message]

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=20051215092536.GA8122@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=safemode@comcast.net \
    /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