News for hackers. Stuff that matters.

A comment on Experiments with disabling the ME on Sandybridge x230. Parent comment

Re:Experiments with disabling the ME on Sandybridge x230 by inyorgroove on Tuesday September 13, 2016 @03:52PM (#12491634)
Hm, well I have always run it headless. Should be possible to make sure the GPU driver isn't ever loaded.
[ Parent | on HN ]
Re:Experiments with disabling the ME on Sandybridge x230 by erlehmann_ on Tuesday September 13, 2016 @04:11PM (#12491801)
> The Raspberry Pi boots from its GPU and only non-free software is currently available for the GPU, even starting the machine requires a large (2MB) blob of non-free, unsupportable software

https://wiki.debian.org/RaspberryPi

[ Parent | on HN ]
Re:Experiments with disabling the ME on Sandybridge x230 by ashitlerferad on Tuesday September 13, 2016 @10:36PM (#12493894)
Also from that page:

Broadcom publicly released some code, licensed as 3-Clause BSD, to aid the making of an open source GPU driver. The "rpi-open-firmware" effort to replace the VPU firmware blob started in 2016: https://github.com/christinaa/rpi-open-firmware. See more at https://news.ycombinator.com/item?id=11703842

[ Parent | on HN ]
Re:Experiments with disabling the ME on Sandybridge x230 by LukeShu on Tuesday September 13, 2016 @03:59PM (#12491686)
The VC4 GPU actually is the primary chip; it boots the ThreadX operating system on the VC4 first, then ThreadX loads the user-configured system onto the ARM core. Whether you run headless or not, ThreadX is running on the VC4.
[ Parent | on HN ]