From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: The PCI ID Repository
Date: 4 Nov 2001 18:10:22 -0800 [thread overview]
Message-ID: <9s4see$egc$1@cesium.transmeta.com> (raw)
In-Reply-To: <20011104170202.A3370@ucw.cz> <200111050044.fA50i8o182130@saturn.cs.uml.edu>
Followup to: <200111050044.fA50i8o182130@saturn.cs.uml.edu>
By author: "Albert D. Cahalan" <acahalan@cs.uml.edu>
In newsgroup: linux.dev.kernel
>
> Tundra provides an example: Universe, Universe II, Universe IIB
>
> These chips are the same device in some sense; they are all
> PCI-to-VME bridges. (damn popular too) The programming interface
> is incompatible, so they get different revisions. Tundra isn't
> alone in interpreting the PCI spec this way.
>
Another interpretation, which seems pretty common (we use this one at
Transmeta, for example) is to treat the version ID as the "minor
revision" (indicating an upward compatible change) and the device ID
as the "major revision" (change this to indicate an incompatible
change in the programming interface.)
Unfortunately PCI doesn't have the very nice "compatible with" list
that ISAPnP has -- that, and the "human readable string" were very
useful features of the ISAPnP spec.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
prev parent reply other threads:[~2001-11-05 2:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-04 16:02 The PCI ID Repository Martin Mares
2001-11-05 0:44 ` Albert D. Cahalan
2001-11-05 2:10 ` H. Peter Anvin [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='9s4see$egc$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.