From: "Frank Ch. Eigler" <fche@redhat.com>
To: Shamik Datta <shamik.datta@gmail.com>
Cc: sid@sources.redhat.com
Subject: Re: Error Building SID..
Date: Thu, 25 Dec 2008 18:45:00 -0000 [thread overview]
Message-ID: <20081225184505.GF4195@redhat.com> (raw)
In-Reply-To: <239b036a0812211557h2d73685pf3ccd01a5ac3d6da@mail.gmail.com>
Hi -
On Mon, Dec 22, 2008 at 05:27:53AM +0530, Shamik Datta wrote:
> [...]
> What SID essentially provides is the low level API for the components
> to talk to each other, the pin, the bus and the attribute interface.
> The config file inter-connects all the components through their these
> interfaces. During the simulation instances are created, at any
> activity on these interfaces, the appropriate function is called, eg,
> pin.driven. I presume for these set of APIs the calling bridge is
> setup in tcl, or something like that?, which enables writing
> components in tcl directly. hopefully more or less correct till now.
Right.
> I see for all the components there are class definitions and
> implementations. Again what SID provides here is the set of .h files
> in the ./sid/include directory which implement some basic and some
> utility functions, for these aforementioned interfaces. The rest of
> the design is completely open. SID provides no infrastructure or asks
> for any protocol here. It is left to the designer to define his
> classes (modules) and functions (interfaces), so as to mimic the
> actual hardware.
Right.
> So, for 'bochs' which was an existing emulation of the x86 processor,
> with SID, you have created its bus, pin and attribute interface and
> now other components can exchange data as well as use the existing
> processor emulation.
Right.
- FChE
next prev parent reply other threads:[~2008-12-25 18:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 21:28 Shamik Datta
2008-12-11 23:50 ` Frank Ch. Eigler
[not found] ` <239b036a0812121037p534a4ca1t759ea754c7ebad62@mail.gmail.com>
[not found] ` <20081212195729.GB1200@redhat.com>
[not found] ` <239b036a0812130700v2ba9e054yb63be621c223b769@mail.gmail.com>
[not found] ` <239b036a0812150100h1330ba92nb89c0597268a8c01@mail.gmail.com>
[not found] ` <20081215175754.GA7910@redhat.com>
[not found] ` <239b036a0812151202y5ed2a0a4y486ce4905503de67@mail.gmail.com>
2008-12-15 20:39 ` Frank Ch. Eigler
[not found] ` <239b036a0812211557h2d73685pf3ccd01a5ac3d6da@mail.gmail.com>
2008-12-25 18:45 ` Frank Ch. Eigler [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-31 13:45 Error building SID badiu raz
2007-10-31 14:58 ` Dave Brolley
2007-10-31 17:25 ` Dave Brolley
2004-05-04 12:18 error " Ashutosh Vyas
2004-05-05 0:47 ` Ben Elliston
2004-05-05 8:58 ` Robert Cragie
2004-05-05 9:49 ` Ashutosh
2004-05-06 1:58 ` Ben Elliston
2004-05-07 10:00 ` Robert Cragie
2004-05-07 17:18 ` Frank Ch. Eigler
2003-06-20 21:17 Partha Palit
2003-06-20 21:31 ` Frank Ch. Eigler
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=20081225184505.GF4195@redhat.com \
--to=fche@redhat.com \
--cc=shamik.datta@gmail.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).