From: "Stephen P. Becker" <geoman@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] shmem
Date: Wed, 31 Aug 2005 09:36:30 -0400 [thread overview]
Message-ID: <4315B25E.5040906@gentoo.org> (raw)
In-Reply-To: <4315400D.2030508@gentoo.org>
> David: If you want to get a head start tackling this, try this idea
> (it's what I'm going to do when I get my lazy self back into gear).
> Start with a 2.6.10 mips-kernel to use n32. This will give you a
> somewhat usable kernel with a somewhat usable n32 userland. The
> annoying pthreads bug doesn't appear in this kernel.
I'm not sure this is possible. Remember, he's on ip27, and there were
serious problems getting that to work in <2.6.12.
-Steve
--
gentoo-mips@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-31 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 23:49 [gentoo-mips] shmem spbecker
2005-08-31 5:28 ` Kumba
2005-08-31 13:36 ` Stephen P. Becker [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-11 19:01 spbecker
2005-08-11 19:12 ` David Cummings
2005-08-11 19:23 ` Ciaran McCreesh
[not found] <dbce9302050810121728becc46@mail.gmail.com>
2005-08-10 19:52 ` David Cummings
2005-08-11 0:41 ` Stuart Longland
2005-08-11 4:32 ` David Cummings
2005-08-11 18:10 ` David Cummings
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=4315B25E.5040906@gentoo.org \
--to=geoman@gentoo.org \
--cc=gentoo-mips@lists.gentoo.org \
/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