From: "Kevin D. Kissell" <kevink@paralogos.com>
To: Deng-Cheng Zhu <dengcheng.zhu@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [Q] enabling FPU for vpe1
Date: Wed, 04 Aug 2010 01:09:11 -0700 [thread overview]
Message-ID: <4C592027.8010902@paralogos.com> (raw)
In-Reply-To: <AANLkTinCjSTE7sYa7JdqwAEe-4nZJKAvVfg5q4YVVqC7@mail.gmail.com>
Check the MIPS MT spec. If I recall correctly, it's possible to enable
access to the FPU by either VPE by setting the right bits while the
processor is in the MT configuration mode.
Deng-Cheng Zhu wrote:
> Hi,
>
>
> I'm working on a 34Kf CPU. I understand that only one TC can use the
> FPU at any given time.
>
> My question is: If a TC is attached to the 2nd VPE (i.e. VPE1), can I
> enable FPU for it?
>
> I experimented on this, but failed to do it. Am I missing something?
>
>
> Thanks
>
> Deng-Cheng
>
>
next prev parent reply other threads:[~2010-08-04 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 7:02 [Q] enabling FPU for vpe1 Deng-Cheng Zhu
2010-08-04 8:09 ` Kevin D. Kissell [this message]
2010-08-04 10:14 ` Deng-Cheng Zhu
2010-08-04 15:26 ` Kevin D. Kissell
2010-08-05 1:58 ` Deng-Cheng Zhu
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=4C592027.8010902@paralogos.com \
--to=kevink@paralogos.com \
--cc=dengcheng.zhu@gmail.com \
--cc=linux-mips@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