From: Petr Tesarik <ptesarik@suse.cz>
To: Sergey Brutyan <sergey_brutyan@ehayq.am>
Cc: Stefan Wahren <wahrenst@gmx.net>, linux-arm-kernel@lists.infradead.org
Subject: Re: ARM core blob list
Date: Tue, 24 Sep 2019 13:06:39 +0200 [thread overview]
Message-ID: <20190924130639.5485a21a@ezekiel.suse.cz> (raw)
In-Reply-To: <214b72fe-3162-6c7b-dd6a-ddba9e5851ce@gmx.net>
On Fri, 20 Sep 2019 18:36:50 +0200
Stefan Wahren <wahrenst@gmx.net> wrote:
> Hi Sergey,
>
> Am 20.09.19 um 12:15 schrieb Sergey Brutyan:
>[...]
> > Broadcom BCM2837
>
> here is the list for Linux 5.3:
>
> cpufreq/raspberrypi-cpufreq.c
> gpio/gpio-raspberrypi-exp.c
> clk/bcm/clk-raspberrypi.c
> staging/vc04_services/bcm2835-audio/bcm2835-pcm.c
> staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
> staging/vc04_services/bcm2835-camera/mmal-vchiq.c
> firmware/raspberrypi.c
> hwmon/raspberrypi-hwmon.c
> soc/bcm/raspberrypi-power.c (*)
>
> (*) There is already a blob-free driver called soc/bcm/bcm2835-power.c,
> but it still needs improvements.
>
> Since the ARM cores doesn't have full access, it may not possible to
> replace all these drivers. An alternative approach for blob-freeness on
> BCM2837 would be an open VC4 firmware [1].
>
> [1] - https://github.com/christinaa/rpi-open-firmware
This project has been on hold. Note that the VC4 platform itself is
reverse-engineered, and there is no official support in binutils and
gcc, although it might be possible to rebase the existing code on a
more current version.
Another caveat is that the above firmware project was meant to be
loaded directly by the ROM code, i.e. it would replace bootcode.bin on
a RPi3. With RPi4, this code has moved into the EEPROM and requires a
signature, otherwise the ROM code will refuse to run it.
AFAICT it should be possible to build the open firmware as start.elf or
start4.elf, which need not be signed.
If you're still interested, feel free to contact me.
Good luck!
Petr T
> Good luck
>
> Stefan
>
> > Realtek RTD1395
> > MediaTek MT7623N
> >
> >
> > And also please offer us which is the best SoC for blob-free linux
> > development.
> >
> > Best regards. Sergey.
> >
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-24 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 10:15 ARM core blob list Sergey Brutyan
2019-09-20 16:36 ` Stefan Wahren
2019-09-24 11:06 ` Petr Tesarik [this message]
2019-09-25 9:28 ` Neil Armstrong
2019-09-25 11:02 ` Maxime Ripard
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=20190924130639.5485a21a@ezekiel.suse.cz \
--to=ptesarik@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sergey_brutyan@ehayq.am \
--cc=wahrenst@gmx.net \
/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