All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: Mark Pilon <mpilon@midrivers.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: debugging, kernel port status update
Date: Tue, 23 Oct 2001 18:01:24 -0400	[thread overview]
Message-ID: <3BD5E8B4.ED0BD911@mvista.com> (raw)
In-Reply-To: 3BD5DE9F.17679D05@midrivers.com


Mark Pilon wrote:

> 0) I built a generic binutils/gcc/glibc for the PPC -- notes
> available.

It's probably easier just to download this from someplace like mvista.com.

> I may have to tweak this compiler if I get FPU support along w/
> instructions which aren't a part of this uP's instruction set.

There should be sufficient options to the compiler that wouldn't
require rebuilding.  I suspect telling it to use a 603 core with 405
instruction scheduling will make it work.  Actually, just a 603
will make it work, the additional scheduling hints may improve
performance.

The bigger challenge is the kernel mofication necessary to properly
context switch the FPU on this part.

> -- the #if 0 portion was what was already in head_4xx.S (w/o the if 0)
> but didn't work. the #else case was taken from head.S and seemed to
> work.

You are working with a really old kernel.  Find a newer one.  I would
recommend the 2_4_devel tree for what you are doing.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-10-23 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-23 21:18 debugging, kernel port status update Mark Pilon
2001-10-23 22:01 ` Dan Malek [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=3BD5E8B4.ED0BD911@mvista.com \
    --to=dan@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mpilon@midrivers.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 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.