From: DJ Delorie <dj@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb@sourceware.org
Subject: Re: is sim/common documented anywhere?
Date: Wed, 22 Aug 2012 23:42:00 -0000 [thread overview]
Message-ID: <201208222341.q7MNfg9Y017675@greed.delorie.com> (raw)
In-Reply-To: <201208221923.15833.vapier@gentoo.org> (message from Mike Frysinger on Wed, 22 Aug 2012 19:23:15 -0400)
I've read through the comments and README. Mostly what's missing is
some guide to help tell people where to begin, what parts to worry
about, and WHY you'd use any given piece.
Example: how do I set up the chip's RAM/ROM regions? Do I want them
to be user-configurable? If so, what's the best way to manage them?
I could look at the other simulators and see what functions they call,
then muddle through the comments to try to figure out something
appropriate to pass them, but none of that means I know what I'm doing
or why I'm doing it.
next prev parent reply other threads:[~2012-08-22 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 22:58 DJ Delorie
2012-08-22 23:23 ` Mike Frysinger
2012-08-22 23:42 ` DJ Delorie [this message]
2012-08-23 1:12 ` Mike Frysinger
2012-08-24 20:04 ` DJ Delorie
2012-08-24 22:10 ` Mike Frysinger
2012-08-25 0:50 ` DJ Delorie
2012-08-25 5:32 ` Mike Frysinger
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=201208222341.q7MNfg9Y017675@greed.delorie.com \
--to=dj@redhat.com \
--cc=gdb@sourceware.org \
--cc=vapier@gentoo.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