From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Jose E. Marchesi" <jemarch@gnu.org>
Cc: cgen@sourceware.org
Subject: Re: Hi there
Date: Thu, 19 Jan 2012 21:04:00 -0000 [thread overview]
Message-ID: <20120119210434.GC4174@redhat.com> (raw)
In-Reply-To: <87d3afmmp0.fsf@gnu.org>
Hi -
On Thu, Jan 19, 2012 at 10:01:15PM +0100, Jose E. Marchesi wrote:
> [...]
> Which simulator framework are you planning to use (gdb/sim vs. sid)?
>
> gdb. I am still in the stage on getting familiar with the common sim
> infrastructure, but it looks like it provides enough flexibility (in
> terms of buses, signals, etc) for my purposes.
OK. sid's flexibility may become needed if you want to model more
peculiar hardware, like different cpus, unusual peripherals, but you'll
know when/if you get there.
> Besides, my company filed a copyright assignment for gdb, and I have got
> a personal one in place as well :)
OK.
> BTW, do I need to sign separated papers for CGEN?
What you have should be fine. We have lots of (C)FSF .cpu files in
the /src/cpu repo.
- FChE
next prev parent reply other threads:[~2012-01-19 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 19:18 Jose E. Marchesi
2012-01-19 19:20 ` Frank Ch. Eigler
2012-01-19 21:01 ` Jose E. Marchesi
2012-01-19 21:04 ` Frank Ch. Eigler [this message]
2012-01-19 21:30 ` Jose E. Marchesi
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=20120119210434.GC4174@redhat.com \
--to=fche@redhat.com \
--cc=cgen@sourceware.org \
--cc=jemarch@gnu.org \
/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).