* OCP Vendor/Device IDs
@ 2002-09-12 3:44 David Gibson
0 siblings, 0 replies; only message in thread
From: David Gibson @ 2002-09-12 3:44 UTC (permalink / raw)
To: Armin Kuster; +Cc: linuxppc-embedded
On the whole, I think the new OCP stuff is a step in the right
direction. However, I think the PCI-like Vendor/Device IDs are
unecessary complexity. They make sense in PCI because they're
provided by the hardware, but they're just made up numbers for OCP.
IMO, we'd be better off using ID strings - these can match the device
names given in the user manuals which are about the closest thing we
have to a manufacturer supplied device ID. In any case because the
identifiers are necessarily arbitrary, we might as well make them
vaguely memorable strings, rather than random pairs of 16-bit numbers.
PCI and OCP are very different buses, we shouldn't expect the code for
them to look too similar. OCP should be *much* simpler than PCI.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-09-12 3:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-09-12 3:44 OCP Vendor/Device IDs David Gibson
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).