All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Borg <kentborg@borg.org>
To: linux-kernel@vger.kernel.org
Subject: Loading init and ld.so.1 for Coldfire V4e
Date: Tue, 8 Oct 2002 15:54:15 -0400	[thread overview]
Message-ID: <20021008155415.D9391@borg.org> (raw)

I am trying to get Linux working on a Coldfire V4e (no, they don't
exist yet in the outside world).  This is kind of an m68k, but being a
Coldfire, it is a subset of the old m68k.  This is a Coldfire, but
being new and spiffy, it has an MMU (32 instruction TLB entries, 32
data TLB entries). 

Currently I am at the point where a lot of the memory stuff is
possibly working, the kernel thinks it has booted, and it is trying to
fire up init.  And it is failing.

Does anyone have a pointer to something I can read to tell me a bit of
how programs load, what ld.so.1 does, etc?  I am in the midst of elf
headers, I see ld.so.1 being opened, I see sections with various
addresses flying by, and I end up trying to execute an address that is
not executable, only read-write.  It is possible that stuff really is
percolating correctly from vma's to page tables, it is possible stuff
really is percolating correctly from page tables to TLBs.  It is
possible that ld.so.1 and init really are being built correctly and
even at sensible addresses, but I don't know.  There are too many
variables here that I don't know about.

Any suggestions on where I could learn more on how init is supposed to
get up and running?


Thanks,

-kb, the Kent who happens to work for an obscure little corner of
Motorola.

             reply	other threads:[~2002-10-08 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 19:54 Kent Borg [this message]
2002-10-08 21:40 ` Loading init and ld.so.1 for Coldfire V4e Erik Andersen
2002-10-09 15:14   ` Kent Borg
2002-10-09 15:19     ` Ben Collins

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=20021008155415.D9391@borg.org \
    --to=kentborg@borg.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.