Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Michael Uhler" <uhler@mips.com>
To: "'John Connett'" <jrc@skylon.demon.co.uk>,
	"'Linux MIPS List'" <linux-mips@linux-mips.org>
Cc: "'Jim Gifford'" <maillist@jg555.com>
Subject: RE: MIPS64 NPTL Status
Date: Thu, 22 Sep 2005 13:44:45 -0700	[thread overview]
Message-ID: <00cf01c5bfb6$775e0290$b414a8c0@MIPS.COM> (raw)
In-Reply-To: <43331641.1010604@skylon.demon.co.uk>

If course.  But we haven't announced schedules yet.



/gmu
---
Michael Uhler, Chief Technology Officer
MIPS Technologies, Inc.   Email: uhler at mips dot com
1225 Charleston Road      Voice:  (650)567-5025
Mountain View, CA 94043

> -----Original Message-----
> From: linux-mips-bounce@linux-mips.org 
> [mailto:linux-mips-bounce@linux-mips.org] On Behalf Of John Connett
> Sent: Thursday, September 22, 2005 1:38 PM
> To: Linux MIPS List
> Cc: Jim Gifford
> Subject: Re: MIPS64 NPTL Status
> 
> 
> Jim Gifford wrote:
> > Looking through the latest glibc snapshot they have removed
> > linuxthreads and moved it to ports. I know Daniel has been 
> working on 
> > getting NPTL to work on MIPS32, which it does. Thank you Daniel. I 
> > know from emails I read around linux-mips.org he was going 
> to work on 
> > MIPS64 NPTL, just curious to the status.
> Out of curiosity, is anyone working on using the 
> Multi-Threading ASE to support NTPL?
> -- 
> John Connett
> 
> 

  reply	other threads:[~2005-09-22 20:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22  5:12 MIPS64 NPTL Status Jim Gifford
2005-09-22 20:38 ` John Connett
2005-09-22 20:44   ` Michael Uhler [this message]
2005-09-22 21:30 ` Daniel Jacobowitz
2005-09-22 22:28   ` Jim Gifford
2005-09-22 22:30     ` Daniel Jacobowitz
2005-09-26 15:17     ` Jim Gifford
2005-09-27 13:09       ` Daniel Jacobowitz

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='00cf01c5bfb6$775e0290$b414a8c0@MIPS.COM' \
    --to=uhler@mips.com \
    --cc=jrc@skylon.demon.co.uk \
    --cc=linux-mips@linux-mips.org \
    --cc=maillist@jg555.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