From: Paul Dwerryhouse <paul@dwerryhouse.com.au>
To: Joshua Brindle <JBrindle@snu.edu>
Cc: SELinux@tycho.nsa.gov
Subject: Re: sparc support
Date: Thu, 29 May 2003 08:25:28 +0200 [thread overview]
Message-ID: <20030529062528.GA22122@localhost> (raw)
In-Reply-To: <sed3de3a.002@atlas.snu.edu>
On Tue, May 27, 2003 at 09:52:15PM -0500, Joshua Brindle wrote:
> russel said one of his friends started a sparc port, i was wondering
> if anything had been done on this, particularly i'm interested in the
> wrapper.c for sparc since i know nothing of registers or kernel
> hacking, etc.
That'll be me. It's actually a port to sparc64, since I don't have
access to a plain old sparc processor at the moment. It doesn't work
yet, and I've got stuck, so I haven't done any work on it for a while.
You can download a patch for what I've done so far, here:
http://leapster.org/linux/lsm-sparc64-2.4.20-patch.3
I don't really know what I'm doing, however, so don't expect to see
anything sane there ;)
Basically I've used the i386 patch & Russell's arm port as a guide - so now,
it compiles and boots fine, but it doesn't seem to do what it's
supposed to do, and I didn't know what to do next.
And I'm sure I've screwed up the part for the 32-bit userspace.
Cheers,
Paul
--
Paul Dwerryhouse | PGP Key ID:
Amsterdam, The Netherlands (X) <-> Melbourne, Australia ( ) | 0x6B91B584
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2003-05-29 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 2:52 sparc support Joshua Brindle
2003-05-29 6:25 ` Paul Dwerryhouse [this message]
2003-05-31 0:15 ` Dave Dodge
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=20030529062528.GA22122@localhost \
--to=paul@dwerryhouse.com.au \
--cc=JBrindle@snu.edu \
--cc=SELinux@tycho.nsa.gov \
/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.