dezgeg

10 ms·

121.
by dezgeg 2y ago
Also not so coincidentally the 'fun' to fix debt is often prioritized over critical debt. Case in point, the situation with our flaky/unstable test got so bad that quarter of them are now to set ignore any failures. Pretty mu
122.
by dezgeg 2y ago
It's already been in the mid range (~1 GHz CPU, ~1 GB RAM) embedded systems over half a decade.
123.
by dezgeg 2y ago
The firmware is in control of the clocks, and in case too high of a clock is specified in config.txt it burns a 'warranty void' fuse.
124.
by dezgeg 2y ago
The +x needs to belong inside the {}, ie. "${var+x}" not "${var}+x" But I agree I wouldn't extrapolate too much from one such brain fart
125.
by dezgeg 2y ago
In addition to what you mentioned, the ability to atomically commit to a library and all of its consumers. And for a change to a library run the tests of all of its consumers as well.
126.
by dezgeg 2y ago
I'd be surprised if that was not fixable in the Jetson with pure software changes.
127.
by dezgeg 2y ago
Not true, there are smaller companies providing closed source kernel modules as well. Check any Android image for a device with SD card slot in the era where open source exfat driver didn't exist, and you'll likely find one of the
128.
by dezgeg 2y ago
I assume that's because wear leveling is something that would be implemented purely in software, so there's no much point having such info in a hardware manual.
129.
by dezgeg 2y ago
Mainline kernel tends to have only basic support (if at all) for many SoCs that actually get used in phones, especially full power management support has been lacking.
130.
by dezgeg 2y ago
There's still plenty of embedded shops stuck thinking "it's embedded so only thing performant enough is C++", despite having multicore SoCs with multiple GBs of memory and integrated GPU. But I agree (and certainly hope
131.
by dezgeg 3y ago
It sounded to me that he's just responding to a frequently asked readers question. And I'd guess it's more likely for people to ask such question if they're not familiar with US taxation.
132.
by dezgeg 3y ago
Haven't those people who have years of experience also gone through years of forced MS Office GUI changes?
133.
by dezgeg 3y ago
The same thing has happened in the Linux kernel - there are multiple semi-duplicate SoC USB drivers for the Synopsys core.
134.
by dezgeg 3y ago
Haskell enforces that types and type constructors start with Uppercase, and that everything else starts with lowercase.
135.
by dezgeg 3y ago
Somehow I had thought even in buffered mode the kernel would only accept block-aligned and sized I/O. TIL.
136.
by dezgeg 3y ago
Isn't `nc -l -p 1234 > /dev/nvme0nX` working by accident (relying on that netcat is buffering its output in multiples of disk block size)?
137.
by dezgeg 3y ago
Let's have a concrete example, link() in struct inode_operations is defined as: int (*link) (struct dentry *,struct inode *,struct dentry *); Let's then look at the ext4 implementation of the link() operation: stati
138.
by dezgeg 3y ago
> I need to change the mode of a wifi driver (which I do via modprobe) Is that something that could be added to modprobe.conf to have it work right without any modprobe calls? > Huh, onehsot services are listed as stopped even though
139.
by dezgeg 3y ago
The main problem of buildroot is the fact you need to rebuild from scratch all the time. Yocto has properly working incremental builds. Yocto is definitely more flexible, which can be a curse as it gives architecture astronauts more chances
140.
by dezgeg 3y ago
Even the mechanism predating WALv1 (rollback journal) uses two files. I don't think there is any way of using SQLite crash-proof with just a single file. Besides, even if the database is single-file it's still necessary to use fil
141.
by dezgeg 3y ago
Yeah, I assume it's similar how ARM errata are often worked around - set some bit in an undocumented MSR to disable some microarchitectural optimization. A silicon vendor I worked at called them CYA (Cover Your Ass) bits :)
142.
by dezgeg 3y ago
Unbounded/large offsets are the critical part. Minimum unit where memory protection can be set is one page (4096 bytes on x86), so compiler could reasonably assume that offsets 0-4095 are always safe to dereference (in the sense that S
143.
by dezgeg 3y ago
Try something like this with optimization on: int would_increment_overflow(int a) { if (a + 1 < a) { return -1; return 0; } This gets turned to a function that always returns 0. 0000000000000000 <wou
144.
by dezgeg 3y ago
In huge number of cases the null dereference is not from accessing 0x0 but some offset to it (ie. accessing a struct member or array element that's not the first one). Of course in practice most of the offsets are below the limit where
145.
by dezgeg 3y ago
I'd think it matters for the purposes of what behaviour can be changed by microcode updates, no?
146.
by dezgeg 3y ago
It seems to be in several files, e.g. UI/uiDrawApplication.asm is 1000 lines of asm
147.
by dezgeg 3y ago
https://fearoflanding.com/
148.
by dezgeg 3y ago
Distros like Arch and NixOS use the vanilla kernel with very small amount (single digits) of patches on top. For the purposes of ext4, it's very likely to be as-is with vanilla. (I am counting the official linux-stable releases from ke
149.
by dezgeg 3y ago
Yeah, no. I have a bad feeling that fragmentation will become a mess in RISC-V world. Just few month ago Qualcomm threatened to not support the existing C extension and proposed their own 16-bit instruction set. Also another example of such
150.
by dezgeg 3y ago
Ethernet is already used to transmit radio signal over fiber which requires extremely tight variation in latency (probably more strict than automotive).

More ›