From: David Gibson <david@gibson.dropbear.id.au>
To: Armin Kuster <akuster@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: OCP Vendor/Device IDs
Date: Thu, 12 Sep 2002 13:44:37 +1000 [thread overview]
Message-ID: <20020912034437.GC32156@zax> (raw)
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/
reply other threads:[~2002-09-12 3:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020912034437.GC32156@zax \
--to=david@gibson.dropbear.id.au \
--cc=akuster@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).