ahlCVA

6 ms·

61.
USB-C-ing All The Things(hackaday.com)
28 points by ahlCVA 1y ago|2 comments
62.
Scalable Chrysopoeia via (N,2n) Reactions Driven by Deuterium-Tritium Fusion(arxiv.org)
2 points by ahlCVA 1y ago|0 comments
63.
An almost catastrophic OpenZFS bug and the humans that made it(despairlabs.com)
7 points by ahlCVA 1y ago|2 comments
64.
What Microchip doesn't (officially) tell you about the VSC8512(serd.es)
168 points by ahlCVA 1y ago|100 comments
65.
Detection of cancers three years prior to diagnosis using plasma cell-free DNA(aacrjournals.org)
4 points by ahlCVA 1y ago|1 comments
66.
by ahlCVA 1y ago
Press release: https://www.hopkinsmedicine.org/news/newsroom/news-releases/...
67.
Precision Clock Mk IV(mitxela.com)
552 points by ahlCVA 1y ago|126 comments
68.
Galileo's Testing Communications(berthub.eu)
4 points by ahlCVA 1y ago|0 comments
69.
by ahlCVA 2y ago
I see reproducible builds more as a contract between the originator of an artifact and yourself today (the two might be the same person at different points in time!) saying "if you follow this process, you'll get a bit-identical a
70.
by ahlCVA 2y ago
For me as a developer, reproducible builds are a boon during debugging because I can be sure that I have reproduced the build environment corresponding to an artifact (which is not trivial, particularly for more complex things like whole OS
71.
by ahlCVA 2y ago
My favorite bit of alternate history computer interface standards is UPAMD ( https://en.wikipedia.org/wiki/Universal_Power_Adapter_for_Mo... ) - essentially what USB-C/USB-PD ended up being but using CAN for communi
72.
by ahlCVA 2y ago
Buildroot has package-parallel builds when using BR2_PER_PACKAGE_DIRECTORIES (see https://buildroot.org/downloads/manual/manual.html#top-level... ). It's for some reason still marked as experimental in the doc
73.
by ahlCVA 2y ago
> I also liked the fact that Btrfs is probably super well tested in the Linux kernel by now. btrfs has certainly been around for longer, but in my (embedded systems only) experience, EROFS has been pretty solid - it's slowly being p
74.
by ahlCVA 2y ago
This sounds like a perfect application for EROFS[1]. While it comes from an embedded systems background, it has seen some usage in container use cases and is moving towards a general "mountable tar" application. It would also avoi
75.
by ahlCVA 2y ago
I feel the same, but I've never actually talked to anybody about it since it felt like such a strange thing to say. Thanks for letting me know I'm not alone!
76.
by ahlCVA 2y ago
Fascinating that somebody is using Swift "in production" for that! I work on small-ish embedded Linux systems and I've been looking for an alternative to C for a long time. Rust does not fit the bill, both because I don'
77.
by ahlCVA 2y ago
As a connoisseur of serialization formats, this is intriguing - I wasn't aware there was a schemaful version of msgpack once, and an ad-hoc search doesn't reveal any leads. Can you point me to some information on how that older fo
78.
by ahlCVA 2y ago
It was just a bad fit for the problem at hand. It was picked mainly because there were a bunch of Elixir backend devs in the organization that were out of work and every problem looks like a web service (or any other system architecture you
79.
by ahlCVA 2y ago
I once used CRIU to implement the hacky equivalent of save-lisp-and-die to speed up the startup process of a low-powered embedded system where the main application was misguidedly implemented in Erlang and loading all the code took minutes
80.
by ahlCVA 2y ago
> find an old daisy-wheel printer I'm definitely on board with the analog approach, but this is interesting. What's the reason for recommending a daisy-wheel printer compared to other printing technologies? Is it just that the
81.
by ahlCVA 3y ago
This is a frequently-touted solution, but now somebody compromising printer.lan.example.com can impersonate auth.lan.example.com, which isn't great either.
82.
Vulnerability in golang.org/x/crypto/ssh(groups.google.com)
3 points by ahlCVA 3y ago|1 comments
83.
by ahlCVA 3y ago
> A MITM attacker can arbitrarily delete messages from a connection before the secure channel is established, as sequence numbers are only validated once the channel is established and arbitrary messages are allowed during the handshake,
84.
by ahlCVA 3y ago
This is on point. I work on small-ish embedded Linux systems and I would really like to use Rust there, but a single Rust binary takes up enough space for 10 C programs, so it's prohibitive. You can dynamically link your libraries (esp
85.
by ahlCVA 3y ago
This seems to be the corresponding video (linked in the associated media tab on arXiv): https://sciencecast.org/casts/suc384jly50n
86.
by ahlCVA 3y ago
I missed that development, thanks! As I understand it, it's not strictly muxing per se - you're basically siphoning off the interrupts from the M0 core using a hardware mechanism instead of firmware + IPC, so any firmware you migh
87.
by ahlCVA 3y ago
While the BL808 (what the Ox64 uses) can nominally run Linux, it doesn't really work for that in practice because of design issues in the chip (or to put it differently: it was never designed for that purpose - the C906 core was includ