public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Scott Dattalo <scott@dattalo.com>
Cc: sid@sources.redhat.com
Subject: Re: SID and eCos
Date: Wed, 19 Jun 2002 20:42:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0206192036010.12953-100000@ruckus.brouhaha.com> (raw)
In-Reply-To: <15632.62797.402920.686293@tooth.toronto.redhat.com>

On Wed, 19 Jun 2002, Ben Elliston wrote:

> Hi Scott,
> 
> >>>>> "Scott" == Scott Dattalo <scott@dattalo.com> writes:
> 
>   Scott> After sending my previous message, I noticed that this is already part of 
>   Scott> SID. (Perhaps though, the fancy graphics are missing). I also have 7 
>   Scott> segment LED's http://www.dattalo.com/gnupic/7seg3.gif. 
> 
> Yep.
> 
> A seven segment display component would be a nice introduction to
> using the SID API.  Please consider porting your component.  There is
> plenty of programmer documentation on the web pages.

I will look at it. (But like everyone else, I've got a lot going on - in 
particular, I'm in the middle of porting SDCC to the PIC).

> 
>   Scott> Oh and of course, I almost forgot, gpsim simulates almost every Microchip 
>   Scott> PIC device; everything from the tiny 12-bit core devices, to the popular 
>   Scott> 14-bit core devices, and the less used, but more powerful 16-bit core 
>   Scott> devices. These are essentially modules too.
> 
> These would be great to have in SID, if you're feeling like it!

This will be a little harder. :).

> 
>   Scott> One of the goals for gpsim was speed. On my ancient 450Mhz PIII, gpsim can
>   Scott> simulate a PIC several times faster than real time. This was achieved by
>   Scott> creating an event-driven behavioral simulation model. In essence, the
>   Scott> simulator only simulates the things it needs to simulate. That sounds like
> 
> In general, this is the philosophy of SID components: only simulate
> sufficiently for target software to execute correctly.

Sounds great, Ben! I'll continue to stay subscribed to this list (the 
volume certainly is low) and keep track with what's going on. When the 
SDCC port tapers off, I'll revisit more closely how gpsim could (if can) 
be merged.

BTW, my interest in SID at the moment is to simulate an ARM processor - 
so I'll definitely be a user.

Regards,
Scott

      reply	other threads:[~2002-06-20  3:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 13:51 Scott Dattalo
2002-06-18 15:59 ` Scott Dattalo
2002-06-18 18:46   ` Ben Elliston
2002-06-18 22:06     ` Scott Dattalo
2002-06-19 14:19       ` Ben Elliston
2002-06-19 20:42         ` Scott Dattalo [this message]

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=Pine.LNX.4.44.0206192036010.12953-100000@ruckus.brouhaha.com \
    --to=scott@dattalo.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).