Search
82 results for “chexum”
-
-
TIL That the nice looking slim #SenseCAP Card Tracker T1000-E has two variants, #MeshTastic and #LoraWan - the only difference is that the LoraWan variant is Open Source. So Bigly Open Source in fact, that it has a locked bootloader preventing it from being used with MeshTastic.
In other news, if anyone needs a non-MeshTastic capable LoraWan T1000-E, feel free to ping me...
-
Someone (!523b) just took a #meshtastic #lilygo T-Echo in the air near Amsterdam, at least 4km high, and forwarded node information from dutch nodes from 300km away to Brussels... They disappeared when ~40km away.
-
@nazokiyoubinbou @argv_minus_one in #m68k land the 68008 was a similar 8-bit data path variant of its ancestor, but I hated how Motorola was actually removing features and simplifying the instruction set after the 68020, increasingly relying on emulation for more and more FP instructions. It gave the impression that they themselves are unable to cope with the complexity of their own making…
-
@manx @jeang3nie @kornel Oh, I'm sure #autoconf will go away, as fewer and fewer people understand it, but so far what I've seen, "they are going to reinvent autoconf poorly".
I'm quite partial to the suite (as a dinosaur for sure), despite its opaque architecture mixing sh and m4. Maybe 10% of it is never needed anymore, but the rest still has its purpose.
Even for giflib, ESR himself keeps bolting back old functionality after "abolishing" autoconf.
https://sourceforge.net/p/giflib/code/ci/8bed392c280ad2c237e8bf1beca6f8f68f893e87/log/?path=/Makefile -
I should have known more about the history of the #SinclairC5 and how it’s associated with the #MerthyrTydfil Hoover factory, but it still caught me by surprise to see a specimen in a castle in #Wales.
-
@mhd I was quite fond of Amiga #CLI syntax, which many did not consider a proper #Amiga subsystem because of #BCPL, but it allowed commands to pre-declare the arguments in a uniform, documented way similar to Python’s #argparse.
It’s actually handled by BCPL’s rdargs() function, documented in https://www.cl.cam.ac.uk/~mr10/bcplman.pdf (p68).
1/2
-
@mhd I was quite fond of Amiga #CLI syntax, which many did not consider a proper #Amiga subsystem because of #BCPL, but it allowed commands to pre-declare the arguments in a uniform, documented way similar to Python’s #argparse.
It’s actually handled by BCPL’s rdargs() function, documented in https://www.cl.cam.ac.uk/~mr10/bcplman.pdf (p68).
1/2
-
@mhd I was quite fond of Amiga #CLI syntax, which many did not consider a proper #Amiga subsystem because of #BCPL, but it allowed commands to pre-declare the arguments in a uniform, documented way similar to Python’s #argparse.
It’s actually handled by BCPL’s rdargs() function, documented in https://www.cl.cam.ac.uk/~mr10/bcplman.pdf (p68).
1/2
-
@mhd I was quite fond of Amiga #CLI syntax, which many did not consider a proper #Amiga subsystem because of #BCPL, but it allowed commands to pre-declare the arguments in a uniform, documented way similar to Python’s #argparse.
It’s actually handled by BCPL’s rdargs() function, documented in https://www.cl.cam.ac.uk/~mr10/bcplman.pdf (p68).
1/2
-
@mhd I was quite fond of Amiga #CLI syntax, which many did not consider a proper #Amiga subsystem because of #BCPL, but it allowed commands to pre-declare the arguments in a uniform, documented way similar to Python’s #argparse.
It’s actually handled by BCPL’s rdargs() function, documented in https://www.cl.cam.ac.uk/~mr10/bcplman.pdf (p68).
1/2
-
@didier The best Amigas are where both kind of programs run perfect :)
I've also been known to lsl.l #2,d0 here and there, which almost everyone kept on hating...
-
Staying for a bit more near #WatfordGap, this week visited #BletchleyPark, the #RollrightStones couple more places near #Banbury and #Coventry, the #CastleRing and lots of highway junctions.
-
-
I'm doing some m68k software archeology, and found a patent describing the 68010 virtualisation features. This mistery CPU is referred by the name "VMPD 12" :) Of course, 12 is just the reference to the respective block in the figures, not implying any technical capabilities or marketing identifiers.
#mc68010 #mc68000 #68k