From: Matthias-Christian Ott <matthias.christian@tiscali.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pci_find_class obsolete
Date: Thu, 03 Mar 2005 15:20:02 +0100 [thread overview]
Message-ID: <42271D12.90408@tiscali.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0503031436490.22266@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>Hello list,
>
>
>after switching to 2.6.11-rc5-bk2 (from 2.6.9-rc2), I found that the nvidia
>module (1.0-4996, old, I know) does not compile anymore, because it
>requires pci_find_class():
>
>nv.c:
>static int
>nvos_probe_devices(void)
>{
> ...
> struct pci_dev *dev;
> ...
> dev = pci_find_class(PCI_CLASS_DISPLAY_VGA << 8, dev);
> ...
>}
>
>What function would I need to use, now that pci_find_class is gone?
>
>
>Jan Engelhardt
>
>
Hi!
you have to use pci_get_class (). But have a look at the patches for
6111 on my webiste:
http://unixforge.org/~matthias-christian-ott/index.php?entry=entry050303-082233
Matthias-Christian Ott
next prev parent reply other threads:[~2005-03-03 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 13:40 pci_find_class obsolete Jan Engelhardt
2005-03-03 14:20 ` Matthias-Christian Ott [this message]
2005-03-03 16:07 ` Jan Engelhardt
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=42271D12.90408@tiscali.de \
--to=matthias.christian@tiscali.de \
--cc=jengelh@linux01.gwdg.de \
--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