From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Pavel Machek <pavel@ucw.cz>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] mobile phones
Date: Wed, 28 Jun 2017 19:04:24 +0300 [thread overview]
Message-ID: <13265343.Sgu0C2fHum@avalon> (raw)
In-Reply-To: <CAK8P3a3WZNbggjn-73b0xuOj3=jUz1AUcTdmXt5a5oMvyiv3sw@mail.gmail.com>
Hi Arnd,
On Wednesday 28 Jun 2017 17:58:27 Arnd Bergmann wrote:
> On Wed, Jun 28, 2017 at 4:38 PM, Linus Walleij wrote:
> >> Graphics acceleration is still missing.
> >
> > The GPU vendor mexican-standoff-farce is bound to become the
> > laughing stock of history. I would put my hopes to the reverse-engineered
> > drivers like Freedreno or the fine work from the etnaviv people.
>
> I agree this is still the fundamental issue, and that Freedreno is our best
> hope at the moment, but aside from that, things have changed a lot over
> the past few years, just not entirely the way we had hoped for:
>
> * Nvidia, Vivante and Broadcom GPUs now all have open drivers, and
> are all still around in their respective niche markets, but have
> completely disappeared from products that are used in phones a few years
> ago.
>
> * PowerVR still has a small market share in phones (ignoring the iPhone),
> but it's mostly used in other markets (TI and Renesas seem to be the
> only loyal customers but have exited the phone market, some others do
> both PowerVR and Mali, with a trend to more of the latter).
> We'll see what happens when someone buys the company.
>
> * This leaves ARM Mali as the only GPU that still matters for phones
> other than Qualcomm's chips. The only ways to solve this are either
> a management change at ARM making it happen officially, or someone
> starting a serious effort to reverse-engineer the Midgard and/or Bifrost
> GPU architectures. At least we have a very clear idea of what would
> need to happen, just nobody who is qualified to do it, willing to spend
> the resources and not already under NDA.
Could we split the problem by finding developers qualified to do it and not
under NDA on one side, people or companies willing to finance the project on
the other side, and put them together ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-06-28 16:04 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 10:48 Pavel Machek
2017-06-25 23:55 ` NeilBrown
2017-06-26 6:43 ` Geert Uytterhoeven
2017-06-26 6:49 ` Tony Lindgren
2017-06-26 11:12 ` Pavel Machek
2017-06-26 11:49 ` Tony Lindgren
2017-06-26 13:14 ` Pavel Machek
2017-06-26 13:49 ` Tony Lindgren
2017-06-26 20:49 ` Pavel Machek
2017-06-27 7:18 ` Tony Lindgren
2017-06-27 12:14 ` Sebastian Reichel
2017-06-27 21:57 ` Pavel Machek
2017-06-28 16:01 ` Sebastian Reichel
2017-06-28 20:27 ` Pavel Machek
2017-07-02 12:03 ` Sebastian Reichel
2017-06-27 21:57 ` Pavel Machek
2017-06-26 8:34 ` Pavel Machek
2017-06-26 11:20 ` Mark Brown
2017-06-26 12:22 ` Pavel Machek
2017-06-27 11:40 ` Mark Brown
2017-06-28 18:37 ` Pavel Machek
2017-07-02 12:11 ` Sebastian Reichel
2017-06-26 22:23 ` Alexandre Belloni
2017-06-27 7:06 ` Pavel Machek
2017-06-27 12:39 ` Sebastian Reichel
2017-06-27 21:57 ` Pavel Machek
2017-06-28 16:45 ` Sebastian Reichel
2017-06-28 21:10 ` Pavel Machek
2017-07-02 11:28 ` Sebastian Reichel
2017-07-02 18:14 ` Pavel Machek
2017-06-26 10:54 ` Mark Brown
2017-06-26 11:14 ` Pavel Machek
2017-06-26 11:49 ` Mark Brown
2017-06-26 12:38 ` Pavel Machek
2017-06-26 16:34 ` Mark Brown
2017-06-27 11:41 ` Sebastian Reichel
2017-06-28 14:38 ` Linus Walleij
2017-06-28 15:58 ` Arnd Bergmann
2017-06-28 16:04 ` Laurent Pinchart [this message]
2017-06-28 16:25 ` Pavel Machek
2017-06-28 18:26 ` Mark Brown
2017-06-28 17:01 ` Pavel Machek
2017-06-28 19:03 ` Tony Lindgren
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=13265343.Sgu0C2fHum@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=pavel@ucw.cz \
/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