From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@puffin.external.hp.com, debian-hppa@lists.debian.org
Subject: Re: A500 status update
Date: Thu, 07 Dec 2000 10:17:10 -0800 [thread overview]
Message-ID: <200012071817.KAA08546@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Thu, 07 Dec 2000 09:16:25 PST." <E1443ib-0003sK-00@noam.fc.hp.com>
Paul Bame wrote:
> This is a pretty big difference from my experience on c3k but I was using
> Friday's bits:
Another variable: I rebuilt my own hppa64 XC from the latest gcc/binutils
I'll try taggart's latest XC bits on the next round.
> Maybe you have some older signal code in your tree? I explicitly tested
> SIGALRM.
Not kernel tree. Very likely my NFS root is stale.
> I've had some problems with syslogd too, but nfsroot-latest it seems
> fine.
hmm....I have that. nfsroot-latest.tar.gz -> nfsroot-20001009.tar.gz
> When I run hwclock by hand I get warnings from the ioctl() syscall
> converter about unknown ioctls, but no crash or anything.
ok. Perhaps it's time to re-enable that.
> There will
> possibly be a LOT of unknown ioctls to translate, and we owe thanks
> to Grant for turning on the skeleton of the ioctl converter stolen
> from sparc/mips (parisc64/kernel/ioctl32.c)
I didn't do that much!
You figured out the 64-bit function pointer crud! :^)
That was the only really b0rken part.
thanks,
grant
Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253
next prev parent reply other threads:[~2000-12-07 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 6:34 [parisc-linux] A500 status update Grant Grundler
2000-12-07 6:49 ` Grant Grundler
2000-12-07 9:56 ` Richard Hirst
2000-12-07 16:16 ` Paul Bame
2000-12-07 18:17 ` Grant Grundler [this message]
2000-12-07 20:46 ` Matthew Wilcox
2000-12-07 22:08 ` Paul Bame
2000-12-08 17:30 ` Matthew Wilcox
2000-12-11 13:49 ` [parisc-linux] " Richard Hirst
2000-12-11 15:37 ` Jes Sorensen
2000-12-11 18:52 ` Richard Hirst
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=200012071817.KAA08546@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=debian-hppa@lists.debian.org \
--cc=parisc-linux@puffin.external.hp.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