From: David Daney <ddaney@caviumnetworks.com>
To: YunQiang Su <wzssyqa@gmail.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: what's the status of little endian support of Octeon?
Date: Mon, 10 Aug 2015 14:57:28 -0700 [thread overview]
Message-ID: <55C91E48.4010007@caviumnetworks.com> (raw)
In-Reply-To: <CAKcpw6XSffSzv+5yQMRUaP0FdM-tG444wL75HffstdwLqvfQ9w@mail.gmail.com>
On 08/10/2015 12:04 PM, YunQiang Su wrote:
> I am wondering about the what the status of Little endian support of
> Octeon in upstream kernel,
> aka Linus tree.
>
I think the kernel.org kernel supports little-endian on OCTEON II and above.
> If not, any plan?
>
> Octeon II:
> Supported now?
>
I think so.
> Octeon III:
> Supported now?
> How about the FPU?
I think so.
Anything that works big-endian, should also work little-endian.
That said, some driver support for OCTEON III may be missing (and OCTEON
II for that matter).
David Daney
prev parent reply other threads:[~2015-08-10 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 19:04 what's the status of little endian support of Octeon? YunQiang Su
2015-08-10 21:57 ` David Daney [this message]
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=55C91E48.4010007@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=wzssyqa@gmail.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