public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Henrik Stokseth" <hstokset@privat.cybercity.no>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Programmatically probe video chipset
Date: Mon, 12 Feb 2001 18:11:40 +0100	[thread overview]
Message-ID: <004501c09516$ddf03520$23f9423e@avenger> (raw)
In-Reply-To: <20010212164358.2762.qmail@web119.yahoomail.com>

Paul Powell <moloch16@yahoo.com> wrote:

> Is there an API or other means to determine what video
> card, namely the chipset, that the user has installed
> on his machine?

for PCI and AGP cards you can scan through the bus and fetch all
vendor:device numbers of type 7 (vga compatible) IIRC and then match them
against a database. i have the code for this if you're interested.
for ISA cards that has PnP functionality you can get the vendor string using
a PnP interrupt service routine, I have never actually done that but i know
that it is possible.
But for most cards you can use the VESA VBE API to fetch the information,
you will have to do this from real/virtual mode afaik.
If you're not interrested in programming hardware you can use the pci
interface in /proc instead which is the best solution if you're running
linux. ;o)

-henrik


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://vger.kernel.org/lkml/

      parent reply	other threads:[~2001-02-12 16:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-12 16:43 Programmatically probe video chipset Paul Powell
2001-02-12 16:50 ` Brian Gerst
2001-02-12 16:54 ` Alan Cox
2001-02-12 17:06 ` Fernando Fuganti
2001-02-12 17:11 ` Henrik Stokseth [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='004501c09516$ddf03520$23f9423e@avenger' \
    --to=hstokset@privat.cybercity.no \
    --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