public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: M.Fehr@brunel.de
To: sid@sources.redhat.com
Subject: xScale and SID
Date: Wed, 15 Oct 2003 11:24:00 -0000	[thread overview]
Message-ID: <OFA97EA369.6AA28738-ONC1256DC0.003EE4A0@brunel.de> (raw)

Hallo SID-Developers,

I am going to develop for an Intel Xscale PXA255. The board will be equiped
with
Flash, Ethernet  and perhaps a CAN - Interface.
I am searching for some simulator and SID looks very interesting to me on
the first view.
But it seems as if there is no simulation available for Xscale
architectures. I
can't estimate how much work it will take to simulate such a hardware -
configuration.

May someone give me a hint about the amount and level of work to do?
Will it be more like a lot of configuration or will it include the
development of new SID-Components?

Thanks a lot - Malte




                 reply	other threads:[~2003-10-15 11:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=OFA97EA369.6AA28738-ONC1256DC0.003EE4A0@brunel.de \
    --to=m.fehr@brunel.de \
    --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).