WallWextra

17 ms·

121.
by WallWextra 12y ago
It is true that exactly the same commands are sent to the genuine and counterfeit components, but on genuine FTDI parts it does literally nothing. Here is a commented decompilation: https://twitter.com/marcan42/status&#
122.
by WallWextra 12y ago
Weren't they written in greek?
123.
by WallWextra 12y ago
No, it's accurate to describe reality rather than hypotheticals.
124.
by WallWextra 12y ago
Meanwhile, in reality, C is a compiled language.
125.
by WallWextra 12y ago
This could be done mostly transparently, with the encryption in the memory controller. Addresses and data are already scrambled with a (non-cryptographic) scrambling code for EMI reasons. Of course, a sufficiently fast hardware crypto core
126.
by WallWextra 12y ago
Also that they like ramming it down everyone's throats.
127.
by WallWextra 12y ago
MIPS had trap on overflow.
128.
by WallWextra 12y ago
The basic problem is that this was chiefly of use to companies making hardware, which is a highly competitive industry with very thin margins compared to software, so they won't pay for anything they don't have to pay for. Only in
129.
by WallWextra 12y ago
I do not understand. Where is the memory backing /proc/pid/cmdline and who in the container has a COW copy of it? If nobody, how can reading it cause more allocations in the container?
130.
by WallWextra 12y ago
Sometimes I wonder how much better off we'd be with something exactly like x86, but with a stack that grows upwards.
131.
by WallWextra 12y ago
The 68k address/data register split is ugly, and the double-indirect addressing modes probably cause more difficulties for a fast implementation than any x86 quirk (though this can be cured with R&D money).
132.
by WallWextra 12y ago
I wouldn't mind more focus on accuracy even among quartz movements. Development of temperature-compensated quartz watch movements seems to have stalled, and most watches with such a movement are only available on the Japanese domestic
133.
by WallWextra 12y ago
The typesetting quality of web browsers doesn't even compare to that of TeX, which uses a dynamic programming algorithm to minimize the "badness" caused by line breaks in various places. This is aside from TeX's ability
134.
by WallWextra 12y ago
The unoffical reason is Xamarin wants too much money.
135.
by WallWextra 12y ago
They did recently announce two fab customers, an FPGA manufacturer and then something else that is also low volume and obscure. So maybe the DoD can make it worth their while.
136.
by WallWextra 12y ago
It seems like this could pose some problem for the DOD, since IBM was the only trusted foundry with a cutting-edge process for logic. Presumably they don't want the government of Abu Dhabi fabbing chips for them.
137.
by WallWextra 12y ago
I do believe SOI has some cost disadvantage, and this contributed to its unnpopularity. The POWER8 chips are huge and probably can't be made cheaply, or to consume sane amounts of power. IBM would have to take a very thin cut to compet
138.
by WallWextra 12y ago
Perhaps this post is already buried, but if anybody is reading, do you know where the row-selection and precharge latencies figure into the numbers he gave? He makes no mention of them.
139.
Memory Latency Components (2011)(sites.utexas.edu)
18 points by WallWextra 12y ago|1 comments
140.
by WallWextra 12y ago
I'd really rather not have my toaster running, e.g., bash, since a toaster will never get firmware upgrades.
141.
by WallWextra 12y ago
Gosh, what a collection. I always feel a little sad when I see collections like this up for sale, since it's obvious that somebody loved them a lot.