Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Brian Foster <brian.foster@innova-card.com>
Cc: "David VomLehn (dvomlehn)" <dvomlehn@cisco.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	"Maciej W. Rozycki" <macro@codesourcery.com>,
	linux-mips@linux-mips.org, libc-ports@sourceware.org,
	"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: MIPS RI/XI & trampolines [was:- [PATCH, RFC] MIPS: Implement the getcontext API ]
Date: Thu, 05 Mar 2009 09:01:04 -0800	[thread overview]
Message-ID: <49B00550.5050303@caviumnetworks.com> (raw)
In-Reply-To: <200903050858.32232.brian.foster@innova-card.com>

Brian Foster wrote:
> On Wednesday 04 March 2009 23:34:16 David Daney wrote:
[...]
>> That said, we do have RI/XI working well in our kernel (for non-stack
>> memory), so it is something we are interested in pursuing.
> 
> David,
> 
>  I am Very Interested in this.  we also want RI/XI,
>  at least for for userland (and, very importantly,
>  including the stack), but haven't yet time to deal
>  with the issue.  (our platform is the 4KSd, which
>  has SmartMIPS (and thus has RI/XI)).
> 
>  is what you have at linux-mips.org someplace?
> 

Not at this time, I will see if we can get it merged for 2.6.30...

David Daney

  reply	other threads:[~2009-03-05 17:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-01  0:12 [PATCH, RFC] MIPS: Implement the getcontext API Maciej W. Rozycki
2009-03-03 16:56 ` David Daney
2009-03-04  8:19   ` Brian Foster
2009-03-04 12:17     ` Daniel Jacobowitz
2009-03-04 16:36       ` David Daney
2009-04-02 13:29         ` Ralf Baechle
2009-04-02 20:06           ` Daniel Jacobowitz
2009-03-04 15:44     ` Ralf Baechle
2009-03-04 22:25       ` David VomLehn (dvomlehn)
2009-03-04 22:25         ` David VomLehn (dvomlehn)
2009-03-04 22:34         ` David Daney
2009-03-05  7:58           ` MIPS RI/XI & trampolines [was:- [PATCH, RFC] MIPS: Implement the getcontext API ] Brian Foster
2009-03-05 17:01             ` David Daney [this message]
2009-04-02 13:38         ` [PATCH, RFC] MIPS: Implement the getcontext API Ralf Baechle
2009-04-16  3:46           ` Markus Gothe
2009-04-17  5:53             ` Ralf Baechle
2009-03-05 15:34   ` Maciej W. Rozycki
2009-03-05 16:58     ` David Daney
2009-03-05 18:23       ` David VomLehn (dvomlehn)
2009-03-05 18:23         ` David VomLehn (dvomlehn)
2009-03-05 21:36         ` Ralf Baechle
2009-03-05 21:39           ` Roland McGrath
2009-03-05 21:53           ` Joseph S. Myers
2009-03-05 22:08             ` David VomLehn (dvomlehn)
2009-03-05 22:08               ` David VomLehn (dvomlehn)
2009-04-02 13:19 ` Ralf Baechle
2009-04-15 20:19 ` Joseph S. Myers
2009-04-15 21:37   ` David Daney
2009-04-18 12:38   ` Ralf Baechle
2009-04-18 17:32     ` Joseph S. Myers
2009-04-20 19:57       ` Maciej W. Rozycki
2009-04-28 19:17       ` Aurelien Jarno
2009-04-28 19:21         ` Philippe Vachon
2009-04-28 20:19         ` Maciej W. Rozycki
2009-04-28 20:53           ` Aurelien Jarno
2009-04-28 21:47             ` Maciej W. Rozycki

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=49B00550.5050303@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=brian.foster@innova-card.com \
    --cc=dvomlehn@cisco.com \
    --cc=libc-ports@sourceware.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@codesourcery.com \
    --cc=macro@linux-mips.org \
    --cc=ralf@linux-mips.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