Well, it’s happened before, so it was bound to happen again: a remote code execution bug was found in APT. And it’s particularly interesting in the context of an age-old debate that has been dragging on in Debian-related circles about the use of HTTPS – a question that has been asked often enough that the answer has its own website now.
How bad was it? What is there to learn from this? And what does it tell us about the importance of HTTPS in package management security?
It’s impossible to discuss Electron without the topic of space being brought up, and once that happens, you have to survive the talk about how storage is cheap today and space just doesn’t matter anymore.
Here is why I think all that is bogus — for bonus points, without any unironic use of the terms “engineering”, “real programmers” and “web developers”
One of the easiest ways to “settle” a technical discussion is to resort to an analogy. It took me three minutes of browsing HN (why do I keep doing that to myself?) to find the first one today. When operating systems and computers are discussed, a car analogy is sure to pop up within minutes.
I want to argue that reasoning by analogy is bad when technology is involved. And, more generally, that analogies and “common sense” are bad things to rely on in matters of science and engineering.
An article about C Portability Lessons for Weird Machines has been making the headlines on the Interwebs lately. It’s full of interesting examples, though none of them are from machines relevant to the last two decades of high-end computing.
I think these lessons are still relevant today, though, and that you should still pay attention to them, and that you should still write “proper” code. Here is why.
If you have resorted to Google after having uselessly pored over AD’s reference manuals, hoping to find at least a proper hint about how to approach this, if not a bit of code, it’s OK, you can stop now. It’s right here. Your quest is complete.
In the hope that no poor soul will have to bang his head against the desk trying to piece together the countless pieces of this puzzle, I did a quick write-up to show you how to do SPI communication with DMA on ADSP-21489. This should probably work (with obvious adaptation) on any DSP in the same family, and it should be easy to adapt if your DSP is the SPI slave, not the master, as below.
We are nearing the twenty-year anniversary of the Halloween documents, and in this context, I find myself routinely answering the same question: why is Azure so important for Linux and Microsoft? Why is it such a big deal?What’s this EEE that old people keep talking about?
There is a part of writing a Linux BSP that I dread profoundly, and it’s among the most trivial ones. Specifically, I’m talking about that part where you’ve written a new device driver, or modified something in an old one, or you just need to configure it. You’ve added the right incantation in the device tree, you boot, and nothing happens. The module isn’t probed, or your changes are silently ignored.
If you’d have told me five years ago that soon enough I will be able to drop a Cortex M IP in my design, at no price at all, there is a good chance that I would have said something snarky about optimism and how harsh reality actually is.
And yet here we are. Arm just started giving Cortex M IP cores away.