As of todays #linux-next (https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tag/?h=next-20210112) you can run the #librem5devkit without any additional patches using the default mainline arm64 #defconfig. This means distributions can enable it without trouble from #linux 5.12 onwards. The #librem5 itself needs some more work but it builds a lot on what we have for the devkit.
I have an opening for a short term Security analyst to do GRC Assessments against NIST 800-53.
Contract is 100% remote, and through the end of the year.
This is a intermediate role who will be working with a lead analyst.
If you are interested, send an email to thegibson (at) blackfiresec (dot) com
The PeerTube content bootstrap fund:
Szanowni rodacy, zapraszam do zapoznania się krótką dyskusją o "zaniechaj" i "anuluj":
"Okna dialogowe pola obrazu" i "uwiąż":
"Sterowanie pokazem przeźroczy":
Piłeś? Nie tłumacz!
Wow, that was quick: Thanks to Lucas Stach our #etnaviv runtime power managemt fix already landed in linux-next: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?qt=range&q=ea4ed4a55f7363ad8db1863bd536548fb7e5c6aa..78f2bfa3181cd7ee134274aa17177dd933c69dc1
The fix hits the #librem5 with the next kernel update.
I hear the "you shouldn't have to learn how your engine works just to drive a car" argument often used to counter my insistence on learning git's internals to understand its externals.
My response: git is a tool for professionals. Racecar drivers should definitely understand how engines work. Amateur users of version control systems are using the undo and redo buttons in a Google Document. Git is a professional tool and if you're a professional then you have a professional obligation to learn your tools properly.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.