From: Frank Rowand <frank.rowand@am.sony.com>
To: wuzj@lemote.com
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: the current status of RT_PREEMPT for mips
Date: Tue, 10 Feb 2009 17:16:41 -0800 [thread overview]
Message-ID: <499226F9.5000307@am.sony.com> (raw)
In-Reply-To: <20955.222.92.8.142.1234138032.squirrel@mail.lemote.com>
wuzj@lemote.com wrote:
> HI!
>
> I'm planning to port RE_PREEMPT to loongson2f(a mipsel compatible
> processor), the "FAQ" web page of RTWiKi(rt.wiki.kernel.org) shows that
> "There are systems representing the x86, x86_64, ARM, MIPS, and Power
> architectures using the CONFIG_PREEMPT_RT patch.", does it means that
> RT_PREEMPT support MIPS architecture? because i can not find any more
> information about it, I tried to use the latest RT_PREEMPT on qemu
> 0.9.1/mipssim, it can not boot, so I come to get your help, could you give
> any current status of RT_PREEMPT for mips? such as:
>
> 1. does the latest RT_PREEMPT(for linux 2.6.26.8) support MIPS
> architecture? or any older one support it?
> 2. if Yes, which MIPS processors have been successfully running RT_PREEMPT?
>
> looking forward to your reply, thanks!
>
> Best Regards,
> falcon
I do not have information for current versions of the kernel, but last year
I was running 2.6.24-rt1 on a Toshiba tx4937 to do some experiments.
I have a few trivial patches for the latency tracer, but if you use a newer
kernel they are not needed because ftrace replaced the latency tracer
in 2.6.24-rt2.
-Frank Rowand
Sony Corporation of America
next prev parent reply other threads:[~2009-02-11 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 0:07 the current status of RT_PREEMPT for mips wuzj
2009-02-11 1:16 ` Frank Rowand [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-10 6:12 wuzj
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=499226F9.5000307@am.sony.com \
--to=frank.rowand@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=wuzj@lemote.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 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.