From: "Magne Østlyngen" <magne@spacetec.no>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] So you wanna get to a prompt, eh?
Date: Thu, 21 Oct 1999 12:25:15 +0200 [thread overview]
Message-ID: <380EEA0B.F5E469DB@spacetec.no> (raw)
In-Reply-To: Pine.LNX.4.10.9910191607110.10378-100000@localhost.localdomain
> I've spent most of the afternoon working on the patches sent in by Thomas
> Bogendoerfer, and have extended them to get the kernel working and to a
> functional sash prompt.
> And for those you out there who are interested in helping us test the
> kernel, I've also posted a functional kernel image, for you try. You can
> find it at:
> And not wanted to leave much as an excercise for the reader, I've also
> posted the ramdisk that I used, which has been extended to include
> /dev/console, etc.
Is the ramdisk included in the kernel-image? When I boot the kernel,
I get 'no ramdisk'.
Of course, I don't get further than 'Transferring control to kernel'..
:(
I thought I had a 715, but no, it was a 710 (Bushmaster), and that seems
to make a big difference.
Is anyone working on support for the 700? I could do some work there,
if it was possible to compile the kernel on linux. Is anything being
done on that? (What was the problem?)
The Image-990705 kernel worked. What changed from that to Image-990929?
--
Magne Østlyngen <magne@spacetec.no>
<magne@skybert.org>
next prev parent reply other threads:[~1999-10-21 10:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-19 20:24 [parisc-linux] So you wanna get to a prompt, eh? Christopher Beard
1999-10-21 10:25 ` Magne Østlyngen [this message]
1999-10-21 15:11 ` Alex deVries
1999-10-21 16:06 ` Christopher Beard
1999-10-21 19:54 ` Helge Deller
1999-10-22 14:22 ` Magne Østlyngen
1999-10-22 15:19 ` Grant Grundler
1999-10-22 16:09 ` John David Anglin
1999-10-24 22:52 ` Alex deVries
1999-10-21 15:13 ` Thomas Bogendoerfer
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=380EEA0B.F5E469DB@spacetec.no \
--to=magne@spacetec.no \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox