From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: GDB support for flash: implementation
Date: Tue, 06 Jun 2006 00:59:00 -0000 [thread overview]
Message-ID: <20060606005944.GA7504@nevyn.them.org> (raw)
In-Reply-To: <20060605210238.GA1036@nevyn.them.org>
On Mon, Jun 05, 2006 at 05:02:38PM -0400, Daniel Jacobowitz wrote:
> Jim and I were talking about this earlier and didn't really come to a
> conclusion. I don't like Eflash; I think it's unnecessarily
> complicated, and that it would actually be simpler to ask the target
> to tell us where its flash is.
Jim asked me to expand on this.
What Eflash would basically do would be return a piece of the
target's memory map. So we've always got a little bit of that
map when we need it, and there's a temptation to hold on to it
and get a better picture of the target as we go along. But that's
a bad temptation, because of the incompleteness; so why not
sidestep it and build the map up front?
Either way, at least in some cases, the map will be incomplete.
For instance, it may not indicate where all RAM and I/O devices
are. But this way at least we know where all the flash devices are.
The target won't come along and surprise us later.
Mark asked a related question about writes to flash regions which fail
to use the flash-specific packets; in my opinion, and Jim's, the right
thing to do is still to return an error. I just don't want the error
to convey information needed for the retry.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-06 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 18:34 Jim Blandy
2006-06-05 21:02 ` Daniel Jacobowitz
2006-06-05 21:28 ` Jim Blandy
2006-06-05 22:39 ` Daniel Jacobowitz
2006-06-06 0:59 ` Daniel Jacobowitz [this message]
2006-06-06 2:03 ` Steven Johnson
2006-06-06 3:19 ` Daniel Jacobowitz
2006-06-06 6:16 ` Jim Blandy
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=20060606005944.GA7504@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.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