From: Dan Malek <dan@netx4.com>
To: diekema_jon <diekema@bucks.si.com>
Cc: Dan Malek <dan@netx4.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: EST SBC8260 Linux memory mapping rules
Date: Sat, 20 May 2000 00:47:56 -0400 [thread overview]
Message-ID: <392618FC.F6678E68@embeddededge.com> (raw)
In-Reply-To: m12szKb-001SyZC@bucks
diekema_jon wrote:
> I have loaded the zImage bits at the link address on the SBC8260,
> and that works just fine.
Well, you must have some pretty damn magical tools, because that
certainly will not work based upon the way the code is written.
What do consider the "link address" and "works"?
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-05-20 4:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-20 0:54 EST SBC8260 Linux memory mapping rules diekema_jon
2000-05-20 1:34 ` Dan Malek
2000-05-20 2:49 ` diekema_jon
2000-05-20 4:47 ` Dan Malek [this message]
2000-05-22 16:43 ` Wait Queue bug triggered on EST SBC8260 diekema_jon
2000-05-24 20:14 ` diekema_jon
2000-05-24 20:24 ` Joe Green
2000-05-24 20:29 ` Joe Green
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=392618FC.F6678E68@embeddededge.com \
--to=dan@netx4.com \
--cc=diekema@bucks.si.com \
--cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).