arm-trusted-firmware
ixy-languages
arm-trusted-firmware | ixy-languages | |
---|---|---|
9 | 30 | |
1,823 | 2,108 | |
1.6% | 0.0% | |
9.9 | 0.0 | |
2 days ago | over 1 year ago | |
C | TeX | |
GNU General Public License v3.0 or later | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
arm-trusted-firmware
- A Close Look at a Spinlock
-
This happens more than I'd like to admit.
I have a PinePhone Pro, and I'm trying to figure out a reasonable way to get more than one half of ten minutes of battery life out of it, while still receiving notifications. I figure the best route to go will be to create a service that holds ports open, while the CPU is completely asleep, and either run it on the modem's processor or, as an possibility for the PinePhone Pro, but not the original Pinephone, run it on the m0 core used for power management.
-
Booting Modern Intel CPUs
Arm v7 was a Wild West, but with v8, Arm tried to standardize a lot. The Arm Trusted Firmware is the reference boot firmware implementation for v8+ CPUs: https://github.com/ARM-software/arm-trusted-firmware.
I'd think most of the referece documents can be discovered from that code base.
Relatedly, from the perspective of hands-on programming, the System Programmer's guide is the manual to start with.
-
“Rust is safe” is not some kind of absolute guarantee of code safety
I assure you that there is no lack of skill; that is just what happens over the course of ten years in a 300,000 line code-base and multiple hundreds of contributors: https://github.com/ARM-software/arm-trusted-firmware/blob/master/Makefile
-
The PocketReform is a made-in-Berlin Linux handheld
The ARM Trusted Firmware is what typically runs in the secure world, and it is indeed open source: https://github.com/ARM-software/arm-trusted-firmware
ROM code generally speaking is not open source, but has been dumped on occasion.
- Unpaid social media moderators perform labor worth at least $3.4 million a year on Reddit alone
-
Will we ever get any coreboot / libreboot support or any PSP source code releases??
The reference Trustzone implementation for ARM is open source https://github.com/ARM-software/arm-trusted-firmware , so I really can't think of some reason the ARM license would have to do with it.
-
SMP support for aarch64
SMP support (at least as far as CPU suspend and hotplug goes) is usually handled by TrustZone firmware on aarch64, not by the kernel (see PSCI). If you write your own OS on a bare-metal platform you can of course do what you want, but if you're looking for existing sources that's where you'd have to look. https://github.com/ARM-software/arm-trusted-firmware is a common reference implementation that supports a bunch of platforms, but many others (e.g. all Samsung and Qualcomm phones) also use their own proprietary stuff which is not publicly available.
-
Dissecting the Apple M1 GPU, part III -- Prototype Mesa compiler can now spin a cube
Come again? https://github.com/ARM-software/arm-trusted-firmware
ixy-languages
-
The Garbage Collection Handbook, 2nd Edition
Not really, here it is winning hands down over Swift's ARC implementation.
https://github.com/ixy-languages/ixy-languages
- rust devs in a nutshell
-
So what you doing for the weeknd
You laugh, but ... https://github.com/ixy-languages/ixy-languages
-
Blog post: My perspective on RAII and memory management in C++ and Rust
GC'd languages are designed to leverage GCs, meaning they usually allocate a lot. Some of the more recent ones (C#, Go) have ways around it or to limit it, but in your average GC'd language you have to really bend yourself out of shape to limit allocations (IIRC the Ixy effort / study / thing never managed to make the Java hotpath allocation-free).
- “Rust is safe” is not some kind of absolute guarantee of code safety
-
I wrote a database engine in Typescript
It's kind of funny when you see things like this project: https://github.com/ixy-languages/ixy-languages
-
What are my prospects in web programming, if I don't like JS?
like not-even-in-the-same-ballpark faster. In this realworld example (userspace network drivers in managed languages) JS manages about 20-30% of native code performance, python iirc is below 1%
-
Don’t call it a comeback: Why Java is still champ
- Support for generic-aware value types (struct vs. class) and low-level features like stackalloc: very valuable for high-performance scenarios and native FFI. See for instance https://github.com/ixy-languages/ixy-languages. In comparison, Java doesn't even have unsigned integers. Yes, Project Valhalla is coming someday.
As well, debatable to some folks, but: properties (get/set); operator overloading; LINQ > Java streams; extension methods; default parameters; collection initializers; tuples; nullable reference types; a dozen smaller features
- Reference Count, Don't Garbage Collect
-
Why did you switch from another language to Rust? Do you regret not learning it earlier?
Very bottom of this file https://github.com/ixy-languages/ixy-languages/blob/master/Java-garbage-collectors.md
What are some alternatives?
lru-rs - An implementation of a LRU cache
ctl - The C Template Library
c2rust - Migrate C code to Rust
cats - Lightweight, modular, and extensible library for functional programming.
too-many-lists - Learn Rust by writing Entirely Too Many linked lists
redgrep - ♥ Janusz Brzozowski
darwin-xnu - Legacy mirror of Darwin Kernel. Replaced by https://github.com/apple-oss-distributions/xnu
c-examples - Example C code
docs - Hardware and software docs / wiki
iced_audio - An extension to the Iced GUI library with useful widgets for audio applications
pinephone_modem_sdk - Pinephone Modem SDK: Tools to build your own bootloader, kernel and rootfs
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.