This is the mail archive of the
sid@sourceware.org
mailing list for the SID project.
Re: Error Building SID..
- From: "Frank Ch. Eigler" <fche at redhat dot com>
- To: Shamik Datta <shamik dot datta at gmail dot com>
- Cc: sid at sources dot redhat dot com
- Date: Thu, 25 Dec 2008 13:45:06 -0500
- Subject: Re: Error Building SID..
- References: <239b036a0812111328r2ed15cc6le385c17a20a19dc@mail.gmail.com> <20081211234936.GA1200@redhat.com> <239b036a0812121037p534a4ca1t759ea754c7ebad62@mail.gmail.com> <20081212195729.GB1200@redhat.com> <239b036a0812130700v2ba9e054yb63be621c223b769@mail.gmail.com> <239b036a0812150100h1330ba92nb89c0597268a8c01@mail.gmail.com> <20081215175754.GA7910@redhat.com> <239b036a0812151202y5ed2a0a4y486ce4905503de67@mail.gmail.com> <20081215203852.GB7910@redhat.com> <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