public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Robert Cragie" <rcc@jennic.com>
To: "SID" <sid@sources.redhat.com>
Subject: hw-cpu-openrisc
Date: Fri, 13 Dec 2002 05:27:00 -0000	[thread overview]
Message-ID: <NMEDLDELHPEFHOMFIJBHMEHACJAA.rcc@jennic.com> (raw)

I would like to create a 'hw-cpu-openrisc' CPU component. I have some ideas
about what to do, however I would be very grateful if someone could give me
some definite pointers and an indication of how much effort it would take. I
see the openrisc architecture is there in bfd and cgen already, so that's a
start...

TIA

Robert Cragie, Design Engineer
_______________________________________________________________
Jennic Ltd, Furnival Street, Sheffield, S1 4QT,  UK
http://www.jennic.com  Tel: +44 (0) 114 281 2655
_______________________________________________________________

             reply	other threads:[~2002-12-13 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  5:27 Robert Cragie [this message]
2002-12-13  7:40 ` hw-cpu-openrisc Frank Ch. Eigler
2002-12-23  8:08   ` hw-cpu-openrisc Robert Cragie
2002-12-23  8:53     ` hw-cpu-openrisc Frank Ch. Eigler

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=NMEDLDELHPEFHOMFIJBHMEHACJAA.rcc@jennic.com \
    --to=rcc@jennic.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).