9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] AOpen MX200 Geforce2(32MB)
Date: Fri, 19 Oct 2001 09:10:22 -0400	[thread overview]
Message-ID: <20011019131025.8C70919A80@mail.cse.psu.edu> (raw)

When a generic PCI chip is used by a different vendor in their product
they sometimes have the choice of how to present the vendor and device id.
They can keep them to reflect the original manufacturer of the chip or they
can put in their own (if they have been assigned one and if the chip allows).
In the former case you can often find the extra information in the sub-vendor
fields in the PCI config space. E.g. the Netgear GA622T card I have presents
the vendor+device id as 0x100B+0x0022, which is the id for the National
Semiconductor DP83820 Gig-NIC, and the sub-vendor fields are 0x1385+0x622A
which identifies the vendor as Netgear; the DP83820 has the vendor+device id
wired in.  On the other hand, Netgear GA620T cards, based on the Alteon Tigon
chip, present the vendor+device id as 0x1385+0x630A; like many chips, the
Tigon allows the id to be set from EEPROM on reset.

I don't think it's a question of right or wrong, but I haven't looked
at the recommendations of the controlling bodies.

On Fri Oct 19 07:33:24 EDT 2001, forsyth@vitanuova.com wrote:
> >>It means that your nvidia card has PCI vendor
> >>id 0x10DE and device id 0x0111, the best
> >>way to identify a vga card.  No grubbing
> >>around in the bios.
> 
> usually, but for instance Netgear has a card with the wrong values.
> fortunately, it's an ether card, not a graphics card, and
> their newer versions have the right values.


             reply	other threads:[~2001-10-19 13:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19 13:10 jmk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-19 15:08 forsyth
2001-10-19 11:37 forsyth
2001-10-19  6:43 okamoto
2001-10-19  6:32 Russ Cox
2001-10-19  7:16 ` Lucio De Re
2001-10-19  7:26   ` Boyd Roberts
2001-10-19  6:22 Russ Cox
2001-10-19  1:56 okamoto
2001-10-19  1:44 okamoto
2001-10-19  1:07 okamoto
2001-10-19  0:54 okamoto
2001-10-18 11:54 Russ Cox
2001-10-18 10:06 okamoto
2001-10-18  5:56 okamoto
2001-10-18 10:26 ` pac

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=20011019131025.8C70919A80@mail.cse.psu.edu \
    --to=jmk@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).