linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alex Shnitman <alexsh@hectic.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux on Motorola Sandpoint/PPMC7400
Date: Tue, 29 Aug 2000 20:13:48 +0300	[thread overview]
Message-ID: <20000829201347.A30190@hectic.net> (raw)
In-Reply-To: <39AAF258.B43B901@mvista.com>; from mgreer@mvista.com on Mon, Aug 28, 2000 at 04:14:32PM -0700


Hi, Mark!

On Mon, Aug 28, 2000 at 04:14:32PM -0700, you wrote the following:

> > I've seen that Hard Hat Linux supports the Sandpoint board with
> > MPC8240 and MPC755. We have a 7400 processor there though. Does anyone
> > have any experience with this configuration? Can Linux run on it?
> >
> > Also, is there anything special I should know about booting Linux from
> > dink32? Here's what I did, and how it failed. I got the latest kernel
> > snapshot from fsmlabs (I tried the same with both the latest 2.2 and
> > 2.3 trees).
>
> If you want to use Hard Hat Linux on the Sandpoint, you need to get it from
> Monta Vista's CDK 1.2.  The LSP (Linux Support Package) you're looking for is
> sp8240 (for Sanpoint 8240--also works with a 755/107 combo).  You can find it
> online at ftp://ftp.mvista.com/pub/CDK/1.2/cd/PowerPC/ppc_82xx/RPMS/

I downloaded the kernel and tried it. It starts booting, but it hangs
right after initializing the the OpenPIC. :-( I'll download the source
code tonight and try to look at it, although I don't have much hopes
-- I've never done kernel hacking at that level. At some point you
gotta learn though.

Is there any book that you recommend to get me started? Any other
docs/tips?

> I haven't tested with a 7400 but it should be fairly close if it doesn't work
> right out of the box.  That is, work without altivec.  I don't know what's
> involved to use the altivec support in Linux.

In most kernels I've seen (fsmlabs', and I think yours too) there was
a CONFIG_ALTIVEC option. What does it do?


--
Alex Shnitman                            | http://www.debian.org
alexsh@hectic.net, alexsh@linux.org.il   +-----------------------
http://alexsh.hectic.net    UIN 188956    PGP key on web page
       E1 F2 7B 6C A0 31 80 28  63 B8 02 BA 65 C7 8B BA

/real/ kernel hackers
    dd if=/dev/urandom of=/vmlinuz
and influence the Universal Randomosity Field.
	-- Gaal Yahas

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

  reply	other threads:[~2000-08-29 17:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-28 19:55 Linux on Motorola Sandpoint/PPMC7400 Alex Shnitman
2000-08-28 20:03 ` Gabriel Paubert
2000-08-28 20:35   ` Alex Shnitman
2000-08-28 21:01     ` Gabriel Paubert
2000-08-29 16:43       ` Alex Shnitman
2000-08-28 23:14 ` Mark A. Greer
2000-08-29 17:13   ` Alex Shnitman [this message]
2000-08-29 19:16     ` Mark A. Greer
2000-08-30 18:58       ` Alex Shnitman
2000-08-30 19:20         ` Mark A. Greer
2000-09-03  4:42         ` Bob Doyle
2000-09-04 10:37           ` Adrian Cox
2000-08-30 19:02       ` Alex Shnitman
2000-08-31  0:45         ` Matt Porter
2000-08-30 23:46           ` Dan Malek
2000-08-31 11:13             ` Gabriel Paubert
2000-08-31 15:01               ` Peter Tympanick
2000-08-29 21:27     ` Mark A. Greer
2000-08-29 14:04 ` Tom Roberts

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=20000829201347.A30190@hectic.net \
    --to=alexsh@hectic.net \
    --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).