lkml.org 
[lkml]   [2001]   [Nov]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: The PCI ID Repository
Date
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>
-
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://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:12    [W:0.035 / U:0.276 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site