Re: Pi4 to Pi5 migration

Liste des GroupesRevenir à cs raspberry-pi 
Sujet : Re: Pi4 to Pi5 migration
De : not (at) *nospam* telling.you.invalid (Computer Nerd Kev)
Groupes : comp.sys.raspberry-pi
Date : 16. Jun 2024, 02:06:54
Autres entêtes
Organisation : Ausics - https://newsgroups.ausics.net
Message-ID : <666e3aae@news.ausics.net>
References : 1 2 3 4 5 6 7 8 9 10 11
User-Agent : tin/2.0.1-20111224 ("Achenvoir") (UNIX) (Linux/2.4.31 (i586))
Computer Nerd Kev <not@telling.you.invalid> wrote:
bp@www.zefox.net wrote:
Computer Nerd Kev <not@telling.you.invalid> wrote:
No the code running on the GPU is all written by Broadcom and Linux
software just talks to that, so nothing needs to be compiled for
the GPU in order to use functionality that's in the stock GPU
firmware. The bottleneck at this point seems to be mainly
application developers adding support for the APIs, but this isn't
an issue with compilers, just the usual limits of time, money, and
willpower.
 
Ok, that clarifies things considerably. Is the API public, at least?
Then folks could experiment.
 
Broadcom's API is DispmanX, which some programs have used directly,
but libbrcmEGL is their library that presents an OpenGL interface
and is thus easier to adapt software to. Separately the Linux
kernel now has its own drivers, which are used via Mesa. I'm not
sure how the performance compares, but the Mesa drivers are the
popular ones these days.

At the risk of correcting myself about details that nobody cares
about anyway, it turns out the original work on Mesa's VC4 driver
was led by a Broadcom developer as well. So that would really be
Broadcom's current graphics API. Seems it actually bypasses the
original closed-source firmware running on the VPU, to do that
graphics processing on the CPU instead, which is a bit of a waste
of the GPU's processing abilities. But it seems they preferred that
to opening the sources and build system for the VPU firmware and
improving upon that, though that's still used for hardware
management tasks.

Here's the VC4 driver developer's blog:
https://anholt.livejournal.com/

And their post about being hired by Broadcom to write the GPU
driver for Mesa and the Linux kernel:
https://anholt.livejournal.com/44239.html

More recently the GPU drivers for the RPi4 and 5 have be developed
by Igalia, presumably as sub-contractor for Broadcom since Igalia
took over from the Broadcom developer:
https://www.raspberrypi.com/news/vc4-and-v3d-opengl-drivers-for-raspberry-pi-an-update/
https://www.igalia.com/2023/09/28/Raspberry-Pi-5-Announced.html
https://www.igalia.com/technology/graphics

It's interesting to find out where all this code comes from.
Broadcom have been more involved than I thought.

--
__          __
#_ < |\| |< _#

Date Sujet#  Auteur
5 Jun 24 * Pi4 to Pi5 migration49<bp
6 Jun 24 +* Re: Pi4 to Pi5 migration27druck
6 Jun 24 i`* Re: Pi4 to Pi5 migration26Chris Townley
6 Jun 24 i `* Re: Pi4 to Pi5 migration25druck
6 Jun 24 i  +* Re: Pi4 to Pi5 migration2Deloptes
6 Jun 24 i  i`- Re: Pi4 to Pi5 migration1<bp
6 Jun 24 i  `* Re: Pi4 to Pi5 migration22<bp
6 Jun 24 i   +- Re: Pi4 to Pi5 migration1druck
7 Jun 24 i   +- Re: Pi4 to Pi5 migration1Computer Nerd Kev
7 Jun 24 i   +- Re: Pi4 to Pi5 migration1Pancho
8 Jun 24 i   +* Re: Pi4 to Pi5 migration16<bp
9 Jun 24 i   i`* Re: Pi4 to Pi5 migration15Computer Nerd Kev
9 Jun 24 i   i `* Re: Pi4 to Pi5 migration14<bp
9 Jun 24 i   i  +- Re: Pi4 to Pi5 migration1Theo
11 Jun 24 i   i  `* Re: Pi4 to Pi5 migration12Computer Nerd Kev
11 Jun 24 i   i   `* Re: Pi4 to Pi5 migration11<bp
11 Jun 24 i   i    `* Re: Pi4 to Pi5 migration10Computer Nerd Kev
16 Jun 24 i   i     `* Re: Pi4 to Pi5 migration9Computer Nerd Kev
17 Jun 24 i   i      `* Re: Pi4 to Pi5 migration8<bp
17 Jun 24 i   i       `* Re: Pi4 to Pi5 migration7Ahem A Rivet's Shot
17 Jun 24 i   i        +* Re: Pi4 to Pi5 migration2The Natural Philosopher
17 Jun 24 i   i        i`- Re: Pi4 to Pi5 migration1Ahem A Rivet's Shot
17 Jun 24 i   i        `* Re: Pi4 to Pi5 migration4<bp
17 Jun 24 i   i         `* Re: Pi4 to Pi5 migration3Ahem A Rivet's Shot
18 Jun 24 i   i          `* Re: Pi4 to Pi5 migration2<bp
18 Jun 24 i   i           `- Re: Pi4 to Pi5 migration1Ahem A Rivet's Shot
11 Jun 24 i   `* Re: Pi4 to Pi5 migration2Newyana2
11 Jun 24 i    `- Re: Pi4 to Pi5 migration1<bp
6 Jun 24 `* Re: Pi4 to Pi5 migration21Pancho
6 Jun 24  +* Re: Pi4 to Pi5 migration19<bp
6 Jun 24  i+* Re: Pi4 to Pi5 migration17druck
25 Jun 24  ii`* Re: Pi4 to Pi5 migration16<bp
25 Jun 24  ii +* Re: Pi4 to Pi5 migration6The Natural Philosopher
25 Jun 24  ii i`* Re: Pi4 to Pi5 migration5<bp
25 Jun 24  ii i `* Re: Pi4 to Pi5 migration4Chris Townley
25 Jun 24  ii i  `* Re: Pi4 to Pi5 migration3<bp
26 Jun 24  ii i   `* Re: Pi4 to Pi5 migration2Anssi Saari
26 Jun 24  ii i    `- Re: Pi4 to Pi5 migration1The Natural Philosopher
25 Jun 24  ii +* Re: Pi4 to Pi5 migration5Ahem A Rivet's Shot
25 Jun 24  ii i`* Re: Pi4 to Pi5 migration4<bp
25 Jun 24  ii i `* Re: Pi4 to Pi5 migration3Ahem A Rivet's Shot
26 Jun 24  ii i  `* Re: Pi4 to Pi5 migration2<bp
29 Jun 24  ii i   `- Re: Pi4 to Pi5 migration1<bp
26 Jun 24  ii `* Re: Pi4 to Pi5 migration4druck
26 Jun 24  ii  `* Re: Pi4 to Pi5 migration3Andy Burns
27 Jun 24  ii   +- Re: Pi4 to Pi5 migration1Anssi Saari
27 Jun 24  ii   `- Re: Pi4 to Pi5 migration1druck
16 Jun 24  i`- Re: Pi4 to Pi5 migration1Lawrence D'Oliveiro
16 Jun 24  `- Re: Pi4 to Pi5 migration1Lawrence D'Oliveiro

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal