public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Robert Cragie <rcc@jennic.com>
Cc: sid@sources.redhat.com
Subject: Re: Co-simulation with SID
Date: Tue, 03 Sep 2002 07:35:00 -0000	[thread overview]
Message-ID: <20020903103535.A5661@redhat.com> (raw)
In-Reply-To: <NDBBLOIOMLKELOJBAPAGKEJPCOAA.rcc@jennic.com>; from rcc@jennic.com on Mon, Sep 02, 2002 at 03:05:59PM +0100

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

Hi -


On Mon, Sep 02, 2002 at 03:05:59PM +0100, Robert Cragie wrote:
> I read in the SID Faq-O-Matic that SID has been used with an HDL Simulator.
> Can anyone give me more details on what work was done here 

There was a prototype sid component that, in conjunction with a special
startup shell, interfaced a Synopsis HDL model of some peripheral to a
running SID model of an encompassing computer.  It was a little prototype
of a specialized protocol bridge.  It worked okay, from what I recall.


> and if it is likely to be included in the open source project? 

This is unlikely.  A baby prototype dealing with a third-party 
proprietary tool would not help an open-source project. :-(


> Or give me some pointers as to how I might go about developing 'proxy'
> components which would interact with an HDL simulator?

The size of such bridging code may not be too large, provided that
one designs a decent mapping between the SID and HDL abstractions.
Issues to consider involve whether a slave/master or peer-to-peer
relationship is more appropriate; embedding one sim within another
vs. running separately; how/whether to synchronize simulated time;
configuration & startup.

What do you have in mind?


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-09-03 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02  7:06 Robert Cragie
2002-09-03  7:35 ` Frank Ch. Eigler [this message]
2002-09-04  3:01   ` Robert Cragie

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=20020903103535.A5661@redhat.com \
    --to=fche@redhat.com \
    --cc=rcc@jennic.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).