3 ms·

"Broadcom never opens up anything". True, but from a link in the related article from The Guardian [0] > Broadcom when they developed the original Videocore f

"Broadcom never opens up anything". True, but from a link in the related article from The Guardian [0] > Broadcom when they developed the original Videocore firmware bought a licence for ThreadX from the writer. AIUI, a lifetime licence, it never expires. No royalties or anything like that. Raspberry Pi have modified that firmware many many times over the last 10 years, but no royalties to pay. Many years later the writer of ThreadX sold the thing to Microsoft. So sounds like the RPi folks have a free hand over this firmware and they might be able to open it now? [0] https://forums.theregister.com/post/reply/4735439 https://forums.theregister.com/post/reply/4735439

joezydeco 3y ago
I believe it's wishful thinking. I wish all you RPi fans the best in your endeavor.
- robertlagrant 3y ago
  > I believe it's wishful thinking. Why?
- Andrex 3y ago
  Maybe a clean room recreation is possible? Or are those straws even further out of grasp...
  - bri3d 3y ago
    Sure, and it's been done: https://github.com/christinaa/rpi-open-firmware https://github.com/christinaa/rpi-open-firmware - but that doesn't involve ThreadX source, just some standard reverse engineering work. ThreadX is really the least interesting part of this whole operation in terms of the Raspberry Pi. It's very cool that ThreadX has been open sourced as it offers an additional battle tested and mature alternative to FreeRTOS for new projects. If they're able to get and maintain the various safety certifications for ThreadX under the Eclipse foundation, this could be game-changing in a very different space from the Pi. But in terms of reverse engineering or open sourcing the Raspberry Pi VideoCore blob, open source ThreadX is pretty much a non-event IMO.
seba_dos1 3y ago
FWIW, the firmware is how they implement DRM for camera and codecs.
bri3d 3y ago
ThreadX is just the scheduler / OS functionality. There are tons of other components in the firmware (namely, the parts that actually do things) which are still encumbered by patent and copyright issues, not to mention the DRM modules which are somewhat security-by-obscurity based. It's one step closer to an open Pi firmware in some ways, but probably not a meaningful step.
numpad0 3y ago
The one put under an open license is just one of numerous forks. The code on RasPi is a different fork modified downstream.
- lproven 3y ago
  I believe I said as much in TFA.
sillywalk 3y ago
from your [0] "the Pi5 has a massively reduced firmware (as much as possible is moved to ARM/kernel space). It now does very little." I did a quick search and came up empty. Does anybody have any more info about this?

joezydeco 3y ago

I believe it's wishful thinking. I wish all you RPi fans the best in your endeavor.

robertlagrant 3y ago
> I believe it's wishful thinking. Why?
Andrex 3y ago
Maybe a clean room recreation is possible? Or are those straws even further out of grasp...
- bri3d 3y ago
  Sure, and it's been done: https://github.com/christinaa/rpi-open-firmware https://github.com/christinaa/rpi-open-firmware - but that doesn't involve ThreadX source, just some standard reverse engineering work. ThreadX is really the least interesting part of this whole operation in terms of the Raspberry Pi. It's very cool that ThreadX has been open sourced as it offers an additional battle tested and mature alternative to FreeRTOS for new projects. If they're able to get and maintain the various safety certifications for ThreadX under the Eclipse foundation, this could be game-changing in a very different space from the Pi. But in terms of reverse engineering or open sourcing the Raspberry Pi VideoCore blob, open source ThreadX is pretty much a non-event IMO.

seba_dos1 3y ago

FWIW, the firmware is how they implement DRM for camera and codecs.

bri3d 3y ago

ThreadX is just the scheduler / OS functionality. There are tons of other components in the firmware (namely, the parts that actually do things) which are still encumbered by patent and copyright issues, not to mention the DRM modules which are somewhat security-by-obscurity based. It's one step closer to an open Pi firmware in some ways, but probably not a meaningful step.

numpad0 3y ago

The one put under an open license is just one of numerous forks. The code on RasPi is a different fork modified downstream.

lproven 3y ago
I believe I said as much in TFA.

sillywalk 3y ago

from your [0] "the Pi5 has a massively reduced firmware (as much as possible is moved to ARM/kernel space). It now does very little." I did a quick search and came up empty. Does anybody have any more info about this?