From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Adds general Freescale external debugger support
Date: Mon, 7 Mar 2011 13:05:51 -0600 [thread overview]
Message-ID: <20110307130551.21521691@schlenkerla> (raw)
In-Reply-To: <2239AC579C7D3646A720227A37E026810FAD0B@039-SN1MPN1-004.039d.mgd.msft.net>
On Mon, 7 Mar 2011 01:18:28 -0600
Zang Roy-R61911 <R61911@freescale.com> wrote:
>
>
> > -----Original Message-----
> > From: Michael Schwingen [mailto:rincewind at discworld.dascon.de]
> > Sent: Monday, January 31, 2011 6:50 AM
> > To: Wolfgang Denk
> > Cc: Zang Roy-R61911; u-boot at lists.denx.de; Kumar Gala; Wood Scott-B07421
> > Subject: Re: [U-Boot] [PATCH v2] Adds general Freescale external debugger
> > support
> >
> [snip]
>
> > > Do these need to be enabled by a new #define? What would be the
> > > disadvantages of having these options always enabled, for all
> > > architectures?
> > Always having debug info in the ELF file should not cause problems IMHO,
> > and one set of settings per platform should be enough.
> Including the debug information, size should be consideration.
It doesn't get included in the .bin which is flashed on the target --
you're worried about the developer's hard disk being too small?
-Scott
prev parent reply other threads:[~2011-03-07 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 9:58 [U-Boot] [PATCH v2] Adds general Freescale external debugger support Roy Zang
2011-01-30 19:43 ` Wolfgang Denk
2011-01-30 22:50 ` Michael Schwingen
2011-01-31 10:43 ` Wolfgang Denk
2011-01-31 11:17 ` Michael Schwingen
2011-03-07 7:24 ` Zang Roy-R61911
2011-03-07 7:18 ` Zang Roy-R61911
2011-03-07 19:05 ` Scott Wood [this message]
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=20110307130551.21521691@schlenkerla \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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