Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@puffin.external.hp.com>
To: Ulrich Strelow <ulrich_strelow@yahoo.com>,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Success story on 715/33 and a question
Date: Fri, 24 Mar 2000 06:31:05 -0700	[thread overview]
Message-ID: <20000324063105.A28615@puffin.external.hp.com> (raw)
In-Reply-To: <20000324121539.21840.qmail@web502.mail.yahoo.com>; from Ulrich Strelow on Fri, Mar 24, 2000 at 04:15:39AM -0800

On Fri, Mar 24, 2000 at 04:15:39AM -0800, Ulrich Strelow wrote:
> So now I am trying to do something useful :) with that
> booted kernel. I would like to mount the proc
> filesystem. I am using a very old ramdisk image
> (19991108) because I had trouble with the newer images
> on the 715/33 (no network driver).

I've got a patch to get the 715/old i82596 going right here,
and i'm going to commit it once I am in FC;  my 715/33 starts
sash fine, Hil keyboard works well (including SysRq), nfsroot
works, the framebuffer works at 1bpp (1024x768), and the HIL
mouse generates recognizable data.  This is about what you
should expect when I got around to committing everything.

> Is there a ramdisk image which I can use on a system
> without a network driver ? Or do I need to compile
> sash on HPUX as a SOM executable and build a ramdisk
> image by myself ? Do I have to make any changes to
> ftp://puffin.external.hp.com/pub/parisc/src/sash-2.1-hpux.tar.gz
> ?

Try to move to nfsroot asap - it's easier.  glibc compiles a
(working libc.a) (again, this is only local changes - I'm sure
people will force me to commit everything in FC though), and
ELF binaries linked against it work, so we'll hopefully have an
ELF sash soon.

	Philipp Rumpf

  reply	other threads:[~2000-03-24 13:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-24 12:15 [parisc-linux] Success story on 715/33 and a question Ulrich Strelow
2000-03-24 13:31 ` Philipp Rumpf [this message]
2000-03-26 21:27   ` willy
2000-03-25 20:29 ` Paul Bame
2000-03-26  3:10   ` [parisc-linux] gcc 2.9 Mike Brancato
2000-03-26 21:51     ` willy
2000-03-26 21:10       ` Mike Brancato
2000-03-27  0:29         ` willy
2000-03-28 15:00     ` Brian S. Julin
2000-04-03 15:06     ` [parisc-linux] ALPHA cross compile -- progress Brian S. Julin
  -- strict thread matches above, loose matches on Subject: below --
2000-03-25 12:06 [parisc-linux] Success story on 715/33 and a question Ulrich Strelow

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=20000324063105.A28615@puffin.external.hp.com \
    --to=prumpf@puffin.external.hp.com \
    --cc=parisc-linux@thepuffingroup.com \
    --cc=ulrich_strelow@yahoo.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