From: fche@redhat.com (Frank Ch. Eigler)
To: sid@sources.redhat.com
Subject: Re: hw-cpu-openrisc
Date: Fri, 13 Dec 2002 07:40:00 -0000 [thread overview]
Message-ID: <o5adja7x00.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <NMEDLDELHPEFHOMFIJBHMEHACJAA.rcc@jennic.com>
"Robert Cragie" wrote:
> I would like to create a 'hw-cpu-openrisc' CPU component. I have
> some ideas about what to do [...]
The work includes ...
- adding sid configury for the openrisc target; see sid/config/sidtargets.m4;
will need autoconf/automake runs throughout
- adding sid configuration file generator pieces to sid/bsp/configrun-sid
- populating sid/component/cgen-cpu/openrisc, mostly with cgen-generated files,
plus one or two hand-written ones; the m32r target is amongst the simplest to
use as a base
- testing, perhaps as a dejagnu "baseboard"
With a cgen model already done, this part can be done in days or weeks
or more, depending on details, acquaintance with configury hacking,
and other factors.
- FChE
next prev parent reply other threads:[~2002-12-13 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 5:27 hw-cpu-openrisc Robert Cragie
2002-12-13 7:40 ` Frank Ch. Eigler [this message]
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=o5adja7x00.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.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).