Re: Error Building SID..

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