From: Paul Miach <paul.miach@edion.com>
To: sid@sources.redhat.com
Subject: best options for a wide bus?
Date: Thu, 04 Jan 2001 20:10:00 -0000 [thread overview]
Message-ID: <3A5549AA.6D7DFF4D@edion.com> (raw)
Hi,
I am looking at getting SID to simulate a bus architecture with busses
wider than 32 bits, ideally busses that are a little over 64 bits wide
(256 bit would be nice, but I can hide this within components). From
looking at the code and the demos (should be demo?) I seem to have three
options;
- Use multiple 32 bit busses to reach the required width
- Use "memory" as a pseudo bus
- Extend the bus object/component to cope with more than 32 bits.
In terms of performance (simulator time) and ease of implementation,
what are the trade off in each of the above?
Cheers.
--
Paul Miach
next reply other threads:[~2001-01-04 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 20:10 Paul Miach [this message]
2001-01-04 20:20 ` Ben Elliston
2001-01-05 5:22 ` Frank Ch. Eigler
2001-01-05 5:39 ` Ben Elliston
2001-01-11 21:14 ` matthew green
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=3A5549AA.6D7DFF4D@edion.com \
--to=paul.miach@edion.com \
--cc=sid@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).