From: Wolfgang Denk <wd@denx.de>
To: Jerry Van Baren <vanbaren_gerald@si.com>
Cc: "Kwansuk Kim" <kskim@neowave.co.kr>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: omitted kernel sections
Date: Mon, 26 Jun 2000 18:04:57 +0200 [thread overview]
Message-ID: <200006261604.SAA26982@denx.local.net> (raw)
In-Reply-To: Your message of "Mon, 26 Jun 2000 08:48:36 EDT." <4.3.2.20000626080626.00b482e0@falcon.si.com>
In message <4.3.2.20000626080626.00b482e0@falcon.si.com> you wrote:
>
> Jon Diekema and I tried Wolfgang's "load" flag hint with the EST JTAG
> debugger and were unsuccessful. We were unable to use objcopy to make
Well, IMHO the tools should fit the work, no vice versa. Maybe you
can talk with ETS and ask what's necessary to load a Linux image with
their tools.
I don't use EST right now, so I can't help here. I'm using the Aba-
tron box, and found that Abatron was *very* helpful many times, for
instance by providing a Linux version of their configuration utility
within a few days after I mentioned that I need something like that
(in fact, when I asked for _some_ documentation for the protocol thay
use to access the box, they sent me the full source code of their
tool). If your tool vendor is no so helpful, you know the options :-)
> Dan Malek has rejected the patch in the BitKeeper tree, although Jon
> and I disagree with him. I didn't find Dan's reply in the archives, it
> apparently was a direct reply. His arguments, as I recall (and my
> apologies, Dan, if I get them wrong), are:
>
> * It makes the image larger.
> > Not really, its just some more elf headers that get stripped on loading.
I'm probably with you here.
> * It isn't how everybody uses the load: everybody just strips the elf
> header (pastes on a proprietary(?) header) and uses it as as a raw
> binary image
> > I disagree, we ran into the problem, developers before us ran into
> the problem, and it is coming up again.
Here Dan is right, I think. Normally I just strip the ELF header and
use the file as "binary" image - all the tools I'm using can accept
that.
> * It requires an extra relink step.
> > Not a big deal in my book given the benefits: a valid elf file that
> is loadable by commonly used tools.
Ummm... depends on your definition of "commonly used".
I never needed it myself...
You might also argument that you should be using a firmware which is
capable of downloading a linux image :-)
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
panic: kernel trap (ignored)
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-26 16:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-26 0:53 I am looking for 8xxrom with ethernet(TFTP) jinoung kim
2000-06-26 6:43 ` omitted kernel sections Kwansuk Kim
2000-06-26 8:08 ` Wolfgang Denk
2000-06-26 12:48 ` Jerry Van Baren
2000-06-26 14:40 ` Murray Jensen
2000-06-26 15:18 ` Steven Tarr
2000-06-26 15:46 ` Jerry Van Baren
2000-06-26 16:04 ` Wolfgang Denk [this message]
2000-06-26 16:40 ` Jerry Van Baren
2000-06-26 21:57 ` Dan Malek
2000-06-27 13:42 ` Frank Przybylski
2000-06-26 8:18 ` Matt Porter
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=200006261604.SAA26982@denx.local.net \
--to=wd@denx.de \
--cc=kskim@neowave.co.kr \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=vanbaren_gerald@si.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 NNTP newsgroup(s).