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: Mon, 28 Aug 2000 23:35:44 +0300	[thread overview]
Message-ID: <20000828233543.A23949@hectic.net> (raw)
In-Reply-To: <Pine.HPX.4.10.10008282201290.6537-100000@gra-ux1.iram.es>; from paubert@iram.es on Mon, Aug 28, 2000 at 10:03:26PM +0200


Hi, Gabriel!

On Mon, Aug 28, 2000 at 10:03:26PM +0200, you wrote the following:

> > 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). I set in the Makefile ARCH := ppc and CROSS_COMPILE :=
> > powerpc-linux- (the prefix for the tools that I have installed, on my
> > Debian box, from www.emdebian.org). "make menuconfig", there I made
> > sure I have support for serial console, there I also set the boot
> > command line (PReP command line it says) to "console=ttyS0,9600
> > console=ttyS0 root=/dev/ram" (I don't really have initrd yet, I want
> > to see the kernel booting first). Then make zImage, which compiles
> > fine, "file arch/ppc/boot/zvmlinux" tells me it's indeed a PowerPC ELF
> > image, then I zsrec it to an srec file (I tried all kinds of offsets
> > to that offset, and then it just hangs...
>
> You can't start an ELF image from jumping at it sload address. But I know
> only PPCBUG and OF, not your firmware.

But zsrec (the thing that creates the srecords from the binary file)
strips the 64k ELF header of the kernel image, so it should be fine?
Or shouldn't it? Or did I misunderstand you?

If there's something basic that I don't understand, I'll be very happy
with an RTFM link too! The thing is that I've read through the FMs
that I've found and so far it looks to me as if I'm doing it right.

Thanks!


--
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

"Xenix is the pinnacle of modern UNIX design, and will be used for
many years to come."
	-- Xenix OS API manual

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

  reply	other threads:[~2000-08-28 20:35 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 [this message]
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
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=20000828233543.A23949@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).