Electrical, firmware, and computer product design / contracting services. @OpenPOWERorg member, @coreboot_org certified contractor.
Joined May 2016
- Tweets 569
- Following 4
- Followers 1,048
- Likes 157
9 Photos and videos
Pinned Tweet
19 Jun 2018
Since @FSF is now considering #RYF certification for devices that require binary-only, closed source firmware to operate, such as the #Librem5, we were wondering: should the RYF program be split into two tiers: RYF Basic and RYF Plus? No blobs allowed in the latter, even in ROM!
41%
Yes, a new tier is needed
11%
No, blobs are OK for RYF
48%
Neither. RYF == no blobs!
83 votes • Final results
1
10
18
Raptor Engineering retweeted
14 Dec 2021
Since this has come up a couple times, we'd like to ask if our hard-line open firmware stance is what you all would like to see, or if the P10 concerns are relegated to specific users. Let us know below!
22%
P0 blobs are OK at $3.5k
61%
No, I want open firmware!
17%
Too costly to have blobs
226 votes • Final results
17
11
22
Raptor Engineering retweeted
23 Aug 2021
Dear OSF Community, as you may know, on behalf @InsurgoTech, we are working on #coreboot-based Dasharo Trustworthy Computing for @RaptorEng Talos II and Talos II Lite. Beta testers are welcome! If you want to contribute to the effort, please subscribe to: newsletter.3mdeb.com/subscri…
4
11
Raptor Engineering retweeted
8 Sep 2021
While we applaud the overall extent of source code available for the #POWER10 firmware stack, two key P10-specific firmware components remain closed source at this time. The first is the off-chip OMI DRAM bridge, and the second is the on-chip PPE I/O processor (links below).
8
16
51
8 Sep 2021
With #BigTech asserting so much post-sale control lately over the devices you ostensibly "own" (even previously owner-control friendly players like @IBM), there are nearly no options left for individuals and corporations that value privacy, auditability, and transparency... 😟
8 Sep 2021
Source-free binaries and proprietary, use-restricted license here: github.com/open-power/ocmb-e… -- just one reason we are not doing P10 systems. If @IBM were to release a proper open firmware we would reconsider, but for now P9, *not* P10, is the only owner controlled / secure option.
1
1
10
8 Sep 2021
We believe that, as an open ISA, POWER is still a viable path toward resolving these issues and restoring owner controllable computing to the market. We are very disappointed that @IBM chose not to walk this path with us, but they are just one closed vendor in a crowded market.
1
11
22 Apr 2021
Our Kestrel POWER-based soft BMC continues to mature! Here's a screenshot of its internal Web server, which has fully working firmware upload capability as of this post. Check out the source and start collaborating with us on Kestrel project page! gitlab.raptorengineering.com…
3
12
35
4 Feb 2021
"...vendor was compromised precisely because of their control over their customers' systems, vendor-controlled keys have never been a greater liability to security." Very on-point article from Hugo Landau regarding new firmware challenges on modern systems devever.net/~hl/omi
1
15
19
Raptor Engineering retweeted
23 Jan 2021
#intel rapidly becoming irrelevant to the world x.com/RaptorEng/status/13520…
21 Jan 2021
We're proud to announce Kestrel -- the world's first open HDL / open firmware soft BMC, built on POWER and capable of IPLing existing OpenPOWER systems! Check out the project README at gitlab.raptorengineering.com…, with basic tooling install instructions at gitlab.raptorengineering.com…
3
13
21 Jan 2021
We're proud to announce Kestrel -- the world's first open HDL / open firmware soft BMC, built on POWER and capable of IPLing existing OpenPOWER systems! Check out the project README at gitlab.raptorengineering.com…, with basic tooling install instructions at gitlab.raptorengineering.com…
5
33
87
21 Jan 2021
The Kestrel project is designed on #OpenPOWER, using the open Yosys/NextPNR flow targeting Lattice ECP5 devices. It provides a single POWER core on the soft BMC, and the entire stack builds on POWER9 machines such as the @RaptorCompSys #TalosII and #Blackbird!
1
1
18
21 Jan 2021
We intend to continue developing Kestrel to increase the existing feature set, but as it stands Kestrel is able to rapidly IPL existing OpenPOWER systems. Contributors welcome -- we're excited to see where the community takes this newfound *ahem* POWER!
1
1
11
13 Jan 2021
We've got something interesting coming down the line for anyone interested in FPGA, open HDL, open FPGA tooling, low level IBM #OpenPOWER #POWER9 initialization, and minimal roots of trust...watch this space for the announcement in coming weeks!
1
4
26
Raptor Engineering retweeted
26 Jul 2020
Did you know #OpenPOWER is one of the only ways to get fully open firmware, and a machine that is completely under your control from the very first application of power? Intel and AMD based vendors, even with #coreboot, *cannot* offer this now or with future ports.
3
18
43
Raptor Engineering retweeted
25 Jun 2020
This is extremely serious. If passed into law, Intel, AMD and others would be forced to use the technologies they have already deployed (ME, PSP, TrustZone, etc.) to officially backdoor their products and permanently subvert security on most computers. justice.gov/opa/pr/statement…
5
34
49
9 Jun 2020
As promised -- FSI master core:
gitlab.raptorengineering.com…
FSI slave core:
gitlab.raptorengineering.com…
FSI protocol decoder:
gitlab.raptorengineering.com…
We're excited to be able to offer these ready-to-use components, and eager to see what the community makes with them! 😀
1
5
7
7 Jun 2020
We're about to make it a lot easier to work with IBM #OpenPOWER #OpenFSI -- from open HDL to protocol decode support in libsigrokdecode, our aim is to make working with FSI (as seen on e.g. #POWER8 and #POWER9) practical with open source tools. More to come soon!
1
10
32
7 Jun 2020
FSI is the IBM equivalent to JTAG. It's more advanced in some areas (e.g. CRC support and automatic error correction) and is widely used as the debug interface in lieu of JTAG on IBM systems. And yes, this screenshot came from a #POWER9 system debugging a separate FSI module! 😀
1
12