Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: mlachwani <mlachwani@mvista.com>
To: Ton Truong <ttruong@broadcom.com>
Cc: 'mohanlal jangir' <mohanlaljangir@hotmail.com>,
	linux-mips@linux-mips.org
Subject: Re: NPTL info needed
Date: Thu, 18 Aug 2005 11:22:57 -0700	[thread overview]
Message-ID: <4304D201.2060306@mvista.com> (raw)
In-Reply-To: <200508181804.LAA04568@mon-irva-10.broadcom.com>

This may help:

http://www.linux-mips.org/archives/linux-mips/2005-03/msg00088.html

Thanks
Manish Lachwani

Ton Truong wrote:

> Daniel Jacobowitz announced support for MIPS NPTL a while back (Apr 05),
>complete with patch set for toolchain and kernel.  Check kernel.org archive
>for that.
>
>A uClibc port is being done by Steve Hill and infos can be found here:
>
>http://www.realitydiluted.com/nptl-uclibc/
>
>HTH,
>
>/?TT
>
>-----Original Message-----
>From: linux-mips-bounce@linux-mips.org
>[mailto:linux-mips-bounce@linux-mips.org] On Behalf Of mohanlal jangir
>Sent: Thursday, August 18, 2005 4:11 AM
>To: linux-mips@linux-mips.org
>Subject: NPTL info needed
>
>Does Linux 2.6 have NPTL support for MIPS architecture? A line at 
>http://www.linux-mips.org/wiki/NPTL says "Currently NPTL for Linux/MIPS is 
>work in progress". Where can I get NPTL source? Do I need new/patched 
>compiler and glibc to compile NPTL source? If yes, what are the patches and 
>where can I find them?
>
>Regards,
>Mohanlal
>
>
>
>
>
>
>  
>

  reply	other threads:[~2005-08-18 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-18 11:11 NPTL info needed mohanlal jangir
2005-08-18 11:11 ` mohanlal jangir
2005-08-18 18:04 ` Ton Truong
2005-08-18 18:22   ` mlachwani [this message]
2005-08-19 14:02     ` mohanlal jangir
2005-08-19 14:02       ` mohanlal jangir
2005-08-21 19:34       ` Steven J. Hill
2005-08-21 20:01         ` Chris Wedgwood
2005-08-22 16:59           ` Steven J. Hill

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=4304D201.2060306@mvista.com \
    --to=mlachwani@mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mohanlaljangir@hotmail.com \
    --cc=ttruong@broadcom.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