From: Paul Bame <bame@endor.fc.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] ELF32 kernel
Date: Wed, 01 Mar 2000 16:35:14 -0700 [thread overview]
Message-ID: <E12QIeA-0002KV-00@endor.fc.hp.com> (raw)
It ain't perfect, but the ELF32 kernel booted with an NFS root, ran
sash and fork/exec-ed hellow. Networking didn't work well on a busy
LAN booting on a B180, dunno why, but it worked great on a c360. I
checked in a defconfig per willy's suggestion and all the other changes
are in CVS too on the branch ELF_BRANCH.
There's a problem when I enable CONFIG_PROC_FS where devinet_init()
calls register_sysctl_table() with a ctl_table containing a char*
pointer (for ->procname) containing the value 0x20, which eventually
dies in strlen() at a lower level. The code in devinet_init *may*
be interacting with the __init/__setup stuff we kludged around for SOM.
Maybe a someone who knows this code can take a look at this?
-Paul Bame
next reply other threads:[~2000-03-02 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-01 23:35 Paul Bame [this message]
2000-03-02 21:37 ` [parisc-linux] ELF32 kernel Paul Bame
2000-03-03 22:00 ` Paul Bame
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=E12QIeA-0002KV-00@endor.fc.hp.com \
--to=bame@endor.fc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox