public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@redhat.com>
To: tb@infa.tuwien.ac.at
Cc: sid@sources.redhat.com
Subject: RE: ARM CP15 support?
Date: Thu, 07 Feb 2002 11:24:00 -0000	[thread overview]
Message-ID: <15458.54390.746882.535996@scooby.brisbane.redhat.com> (raw)
In-Reply-To: <2186384BE565D3118BD800500430927636A401@s11infa-com.infa.tuwien.ac.at>

>>>>> "tb" == tb  <tb@infa.tuwien.ac.at> writes:

  tb> yes, I'm strongly interested; but I don't have any experience with Scheme
  tb> and CGen ;-( Do you know some good points to start from?

It's not a requirement that a SID component such as a CPU be written
using CGEN.  In fact, for a small coprocessor, it may not be worth it.
Consider writing your component by hand as an introduction to SID.
The SID programming documentation is up on the web pages.

CHeers, Ben

  reply	other threads:[~2002-02-07 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-07  7:08 tb
2002-02-07 11:24 ` Ben Elliston [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-07  4:24 tb
2002-02-07  6:20 ` Ben Elliston

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=15458.54390.746882.535996@scooby.brisbane.redhat.com \
    --to=bje@redhat.com \
    --cc=sid@sources.redhat.com \
    --cc=tb@infa.tuwien.ac.at \
    /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).