All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex deVries <adevries@thepuffingroup.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Booting the Linux-Kernel....
Date: Fri, 25 Jun 1999 11:28:48 -0400	[thread overview]
Message-ID: <3773A030.C17480A9@thepuffingroup.com> (raw)


I'm forwarding this message from Helge, and I'm making sure that the
mailing list is fixed.

- Alex

-------- Original Message --------
Subject: Booting the Linux-Kernel.... !
Date: Fri, 25 Jun 1999 16:28:53 +0200
From: Helge Deller <helge.deller@ruhr-uni-bochum.de>
Reply-To: helge.deller@ruhr-uni-bochum.de
To: parisc-linux <parisc-linux@thepuffingroup.com>

Hi !

Ok, I commited my changes to the bootloader, so that we now can begin to
start with the real kernel-work.

My changes in the bootloader are not very impressive, and you can
consider it as a big, bad hack,
but it does it´s job (and that is what counts !!). Later we can try to
optimize it...

You have to build your vmlinux on HP-UX (with make vmlinux) and then do
"make Image".
Then you will find the bootable image in /arch/parisc/hp/boot/Image.

The new bootloader reads SOM-Files and places them to their
Origin-Address, which was given in the arch/parisc/Makefile (currently
at 0x80000) and we do not need anymore to write the exec-orgin into the
boot-Image (because it will be done by the linker).

Currently the only problem I have is, that "make dep" doesn´t work with
my HP-UX-Machine, so I do "make dep" with my i386 and have the
Kernel-Tree (hosted on i386) connected via NFS from HP-UX. (Could maybe
someone take a look at this ?).
All compilations were done on HP-UX....

PS: You will see the kernel-banner, a spinng cursor and blinking LED´s,
really impressive :-)

Ok,
Thanks to you all !

Helge Deller.

                 reply	other threads:[~1999-06-25 15:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3773A030.C17480A9@thepuffingroup.com \
    --to=adevries@thepuffingroup.com \
    --cc=parisc-linux@thepuffingroup.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.