From: Philipp Rumpf <prumpf@suse.de>
To: Lyonel VINCENT <lyonel_vincent@hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] building IPL...
Date: Wed, 28 Jul 1999 21:21:24 +0200 [thread overview]
Message-ID: <19990728212124.M21585@suse.de> (raw)
In-Reply-To: <379F52A1.4BB9F81D@hp.com>; from Lyonel VINCENT on Wed, Jul 28, 1999 at 08:57:38PM +0200
> I'm new to this list and I would want to tell you that if you need a
> dumb user to test your kernels, I have some systems roaming around which
> could do (C-class, D-class, G-class, K-class, 705, 712, 735). These are
> test systems and I can reboot them without any problem.
Great. Do you have something set up to boot all of the PA1.1 ones and see
which one come through and where those that don't hang ?
> PPS: I've just built the latest snapshot and my 712 doesn't seem to like
> it... (btw, the 05/07 image works well and correctly detects the
> CPU/frequency/memory...)
I think you ran into our slightly broken Dino detection code. Try to disable
all dino support for the build.
prev parent reply other threads:[~1999-07-28 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-28 18:57 [parisc-linux] building IPL Lyonel VINCENT
1999-07-28 19:21 ` Philipp Rumpf [this message]
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=19990728212124.M21585@suse.de \
--to=prumpf@suse.de \
--cc=lyonel_vincent@hp.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.