From: Wayne Sherman <wsherman@gmail.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>, linux-kernel@vger.kernel.org
Subject: Re: PCI device problem - MMCONFIG, cannot allocate resource region, resource collisions
Date: Thu, 24 May 2007 17:27:13 -0700 [thread overview]
Message-ID: <46562D61.3000107@gmail.com> (raw)
In-Reply-To: <20070524140941.A21491@jurassic.park.msu.ru>
Ivan Kokshaysky wrote:
> Actually, it should be something like this (also untested).
>
> Ivan.
>
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -1690,6 +1690,14 @@ static void __devinit quirk_p64h2_1k_io(struct pci_dev
> *dev)
> }
> DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x1460, quirk_p64h2_1k_io);
>
> +/* Give unknown D-Link network adapters a proper class */
> +static void __devinit quirk_dlink_unknown(struct pci_dev *dev)
> +{
> + if ((dev->class >> 8) == PCI_CLASS_NOT_DEFINED)
> + dev->class = PCI_CLASS_NETWORK_ETHERNET << 8;
> +}
> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_DLINK, 0x4901, quirk_dlink_unknown);
Ivan,
I tried a couple variations of the patch above. It got me further,
but I still wasn't getting the base address assigned properly. I
suspected a bad card, so I tried another one I have here. It is likely
that I have been fighting with bad hardware all this time. The other
card has a known device ID, a proper class code, and does not give
resource allocation errors. I have an e-mail into D-Link to inquire
about the buggy card.
I appreciate both yours and Jesse's help to troubleshoot this problem.
Best Regards,
Wayne Sherman
prev parent reply other threads:[~2007-05-25 0:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 1:42 PCI device problem - MMCONFIG, cannot allocate resource region, resource collisions System Design Works
2007-05-22 2:03 ` Jesse Barnes
2007-05-22 2:36 ` Wayne Sherman
2007-05-22 15:58 ` Jesse Barnes
2007-05-22 23:21 ` Wayne Sherman
2007-05-22 23:31 ` Jesse Barnes
2007-05-23 9:26 ` Ivan Kokshaysky
2007-05-24 0:20 ` Wayne Sherman
2007-05-24 3:08 ` Jesse Barnes
2007-05-24 3:10 ` Jesse Barnes
2007-05-24 10:09 ` Ivan Kokshaysky
2007-05-25 0:27 ` Wayne Sherman [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=46562D61.3000107@gmail.com \
--to=wsherman@gmail.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jbarnes@virtuousgeek.org \
--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