From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linux-mips@vger.kernel.org
Subject: Re: CPUs with EVA support
Date: Wed, 23 Dec 2020 15:46:35 +0100 [thread overview]
Message-ID: <20201223144635.GA15636@alpha.franken.de> (raw)
In-Reply-To: <b6320b6f-ecbd-bd05-1cb2-ac98aa97825b@hauke-m.de>
On Tue, Dec 22, 2020 at 03:46:31PM +0100, Hauke Mehrtens wrote:
> On 12/20/20 8:32 PM, Thomas Bogendoerfer wrote:
> > Hi;
> >
> > I've started looking how to get rid of get_fs/set_fs for MIPS and
> > my current obstacle is EVA support.
> >
> > Looking for CPUs supporting EVA I only found P5600, are there more ?
> >
> > Does someone sell boards with an EVA enabled CPU ?
> >
> > How good is EVA support in qemu ?
> >
> > Thomas.
> >
> Hi,
>
> The InterAptiv CPUs used by Lantiq/Intel/MaxLinear are supporting EVA mode
> and it is used in the default settings of the vendor SDK.
too bad that I lost my access to a GRX350 eval board, but at least
hardware with GRX350&550 is easy to get.
> The SoCs are not supported by mainline Linux kernel, it was tried to add
> them some years ago:
> https://lwn.net/Articles/761729/
> https://lwn.net/ml/linux-kernel/20180803030237.3366-2-songjun.wu@linux.intel.com/
and no updates for that ? Too sad...
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2020-12-23 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 19:32 CPUs with EVA support Thomas Bogendoerfer
2020-12-21 0:38 ` Jiaxun Yang
2020-12-21 7:04 ` Serge Semin
2020-12-21 7:21 ` Jiaxun Yang
2020-12-21 7:37 ` YunQiang Su
2020-12-21 7:49 ` Serge Semin
2020-12-27 22:26 ` Thomas Bogendoerfer
2020-12-28 1:28 ` Jiaxun Yang
2020-12-28 10:47 ` Thomas Bogendoerfer
2020-12-22 14:46 ` Hauke Mehrtens
2020-12-23 14:46 ` Thomas Bogendoerfer [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=20201223144635.GA15636@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=hauke@hauke-m.de \
--cc=linux-mips@vger.kernel.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 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.