had a good laugh at texas instrument proudly advertising "Supports SHA-1 Authentication" as late as 2013 though https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/slus757c.pdf
Discussion
had a good laugh at texas instrument proudly advertising "Supports SHA-1 Authentication" as late as 2013 though https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/slus757c.pdf
this time it failed for a good reason but i'm about to make it fail for horrifyingly nihilistic reasons again
OMG GUESS WHO HAS TWO THUMBS AND NEEDS TO COMPILE THEIR KERNEL FUCKING AGAIN AFTER UPDATING GCC
i'm about to literally fix all of this for everyone but i need to fix this to do everything else
the problem is never ever gcc's fault. the problem is your fucking tooling
sometimes the problem is gcc's fault
for those keeping track at home that will make 4 full compiles of the beautiful collaboration that interfaces with our hardware
A space for Bonfire maintainers and contributors to communicate