arm-trusted-firmware
too-many-lists
arm-trusted-firmware | too-many-lists | |
---|---|---|
9 | 219 | |
1,823 | 3,018 | |
1.6% | 0.7% | |
9.9 | 0.0 | |
1 day ago | 15 days ago | |
C | Rust | |
GNU General Public License v3.0 or later | MIT 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
too-many-lists
-
Towards memory safety with ownership checks for C
You seem to have a preset opinion, and I'm not sure you are interested in re-evaluating it. So this is not written to change your mind.
I've developed production code in C, C++, Rust, and several other languages. And while like pretty much everything, there are situations where it's not a good fit, I find that the solutions tend to be the most robust and require the least post release debugging in Rust. That's my personal experience. It's not hard data. And yes occasionally it's annoying to please the compiler, and if there were no trait constraints or borrow rules, those instances would be easier. But way more often in my experience the compiler complained because my initial solution had problems I didn't realize before. So for me, these situations have been about going from building it the way I wanted to -> compiler tells me I didn't consider an edge case -> changing the implementation and or design to account for that edge case. Also using one example, where is Rust is notoriously hard and or un-ergonomic to use, and dismissing the entire language seems premature to me. For those that insist on learning Rust by implementing a linked list there is https://rust-unofficial.github.io/too-many-lists/.
-
Command Line Rust is a great book
Advent of Code was okay until I encounterd a problem that required a graph, tree or linked list to solve, where I hit a wall. Most coding exercises are similar--those requiring arrays and hashmaps and sets are okay, but complex data structures are a PITA. (There is an online course dedicated to linked lists in Rust but I couldn't grok it either). IMO you should simply skip problems that you can't solve with your current knowledge level and move on.
-
[Media] I'm comparing writing a double-linked list in C++ vs with Rust. The Rust implementation looks substantially more complex. Is this a bad example? (URL in the caption)
I feel obligated to point to the original cannon literature: https://rust-unofficial.github.io/too-many-lists/
-
Need review on my `remove()` implementation for singly linked lists
I started learning Rust and like how the compiler is fussy about things. My plan was to implement the data structures I knew, but I got stuck at the singly linked list's remove() method. I've read the book as well, but I have no clue how to simplify this further:
-
Factor is faster than Zig
My impression from the article is that Zig provides several different hashtables and not all of them are broken in this way.
This reminds me of Aria's comment in her Rust tutorial https://rust-unofficial.github.io/too-many-lists/ about failing to kill LinkedList. One philosophy (and the one Rust chose) for a stdlib is that this is only where things should live when they're so commonly needed that essentially everybody needs them either directly or to talk about. So, HashTable is needed by so much otherwise unrelated software that qualifies, BloomFilter, while it's real useful for some people, not so much. Aria cleaned out Rust's set of standard library containers before Rust 1.0, trying to keep only those most people would need. LinkedList isn't a good general purpose data structure, but, it was too popular and Aria was not able to remove it.
Having multiple hash tables feels like a win (they're optimized for different purposes) but may cost too much in terms of the necessary testing to ensure they all hit the quality you want.
-
Was Rust Worth It?
> Cyclic references can be dealt with runtime safety checks too - like Rc and Weak.
Indeed. Starting out with code sprinkled with Rc, Weak, RefCell, etc is perfectly fine and performance will probably not be worse than in any other safe languages. And if you do this, Rust is pretty close to those languages in ease of use for what are otherwise complex topics in Rust.
A good reference for different approaches is Learn Rust With Entirely Too Many Linked Lists https://rust-unofficial.github.io/too-many-lists/
- What are some of projects to start with for a beginner in rust but experienced in programming (ex: C++, Go, python) ?
-
How to start learning a systems language
Second, once you've finished something introductory like The Book, read Learning Rust With Entirely Too Many Linked Lists. It really helped me to understand what ownership and borrowing actually mean in practical terms. If you don't mind paying for learning materials, a lot of people recommend Programming Rust, Second Edition by Blandy, Orendorff, and Tindall as either a complement, follow-up, or alternative to The Book.
- My team might work with Rust! But I need good article recommendations
-
Conversion?
Learning Rust With Entirely Too Many Linked Lists which highlights a lot of the differences with how you need to structure your code in Rust compared to other languages.
What are some alternatives?
lru-rs - An implementation of a LRU cache
rust - Empowering everyone to build reliable and efficient software.
c2rust - Migrate C code to Rust
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
darwin-xnu - Legacy mirror of Darwin Kernel. Replaced by https://github.com/apple-oss-distributions/xnu
book - The Rust Programming Language
docs - Hardware and software docs / wiki
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
pinephone_modem_sdk - Pinephone Modem SDK: Tools to build your own bootloader, kernel and rootfs
easy_rust - Rust explained using easy English
8VIM - A Text Editor inside a keyboard, drawing it's inspiration from 8pen and Vim.
x11rb - X11 bindings for the rust programming language, similar to xcb being the X11 C bindings