andy_threos_io

9 ms·

1.
by andy_threos_io 1y ago
2010–2024: Wireless voting system for a bank’s annual shareholder meetings. ARM-based handheld terminals with 2.4GHz RF and LDPC error correction Custom embedded OS, base stations, and 3D-printed enclosures
2.
by andy_threos_io 1y ago
Location: EU / Hungary Remote: Yes Willing to relocate: Mostly no, but open if absolutely necessary Technologies: Embedded systems, OS development, C/C++, Assembly, Python, Java, Lua, JavaScript, TypeScript, React Rés
3.
by andy_threos_io 3y ago
With a better coding you don't need more than 8 bits for a move (less for some). The implementation should store a state machine for the game, a struct for each pieces, and also the board with index to the pieces (occupation). There is
4.
Colonizing Mars isn't a rocket problem(centuryofbio.com)
4 points by andy_threos_io 3y ago|3 comments
5.
by andy_threos_io 3y ago
My view that, this code is nice, however IMO there are several ways to make it more portable, and programer friendly, specially the ported assembly code part. Example. In file threadx-master/ports/cortex_a7/gnu/src&#x2F
6.
by andy_threos_io 3y ago
Real world manufacturing machines (CNCs) are using G codes. Like most laser cutters and engraves, Ex. LaserGrbl software for laser machines. G codes in fact have command for arcs. G02 establishes a mode for clockwise circular arcs. G03 esta
7.
New technology could blow away GPT-4 and everything like it(zdnet.com)
102 points by andy_threos_io 3y ago|17 comments
8.
by andy_threos_io 4y ago
win10 is slower on some aspect than win7. (not the bootup, but normal operation)
9.
by andy_threos_io 5y ago
+1000
10.
by andy_threos_io 5y ago
I found this [1] from MS very useful when I designed some PCB inductor coil for a project. It was only 2D, but some 100 lines of code made the development so much easier. [1] https://maker.js.org/
11.
by andy_threos_io 5y ago
Just a not so recent news from the rust compiler: https://blog.rust-lang.org/2021/05/10/Rust-1.52.1.html "The Rust team has prepared a new release, 1.52.1, working around a bug in incremental compilation
12.
by andy_threos_io 5y ago
Nowadays, it's better to use x86_64 only. The 32 bit x86 has many drawbacks. The 64 bit is much cleaner and better in many many ways. -no segmentation, flat address space -better interrupt handling -better system call -more r
13.
by andy_threos_io 5y ago
I know a good number of people who will move away from Linux after Rust get in the kernel.
14.
by andy_threos_io 5y ago
Not a big deal in the age of gigabytes. All sort of magic happens in BIOS, but after transition to 64bit, it should be fine. The only problem is when BIOS programs some kind of hardware (usb), to write things into the memory like descriptor
15.
by andy_threos_io 5y ago
In our operating system (threos [1] ) this is the way the loader works (page fault exception handling code is from the loader task, mapped and running in the owner context) Also if you have permission, you can call CreateThread [2] system c
16.
by andy_threos_io 6y ago
There are other more portable way to do OS wrapper, and maybe faster (but it's not an issue). Just write the wrapper as a C extension module, and in the module make the system call with proper library call. like in the following code:
17.
by andy_threos_io 6y ago
Most of the implementations are unable to handle larger words than the read (64k) buffer. The C is for sure. edit: Also the C implementation will get in infinite loop with more than 64k words
18.
by andy_threos_io 6y ago
I tried it, but the underlying Roswell system isn't perfect at least. Simple Make fails on linux out of the box. And the look&feel and features are very far from emacs.
19.
by andy_threos_io 6y ago
Irq accounting depends on architecture and code usage, e.g. like some kind of barrier (serializing) before the RDTSC. on newer x86_64 the accounting code is around 100-200 cycles, so not a big deal, interrupt return and exit code is more th
20.
by andy_threos_io 6y ago
Solar energy will not run out in the near future (at least 5 billion years, even earth will be destroyed way before the sun run out of fuel), fossil fuels will run out, it does not matter if it's 50, 100 or 1000 years from now, but it
21.
by andy_threos_io 6y ago
As you may already know, we have a HUGE fusion reactor ( fuses 500 million metric tons of hydrogen each second. [1] ) approximately 149.5 million km away, and it's ready and free* in that sense that we don't have to build it, main
22.
Ajit Pai declares 3Mbps uploads are still good enough for you(theverge.com)
2 points by andy_threos_io 6y ago|0 comments
23.
by andy_threos_io 6y ago
The example program presented is not a good solution, it goes against all the rules and recommendations. Your program (made this way) will NOT WORK at all in the near future, ex when the system call number is changed (it's happened).
24.
by andy_threos_io 6y ago
And it's a total lame, bad assembly code. Lacks any kind of material knowledge or practice.
25.
by andy_threos_io 6y ago
/usr/lib/system/libsystem_kernel.dylib
26.
by andy_threos_io 6y ago
you don't know about it /usr/lib/system/libsystem_kernel.dylib ex. https://stackoverflow.com/questions/37656016/osx-setgid-syst...
27.
by andy_threos_io 6y ago
The system call library is NOT libc.
28.
by andy_threos_io 6y ago
nope, every decent OS has system call library you can write like: bl _Open ; whatever syscall name you have and the linker or the OS dynamic linker will get you the proper system call code, with the numbers. BTW even in our small thr
29.
by andy_threos_io 6y ago
Prime example of how you NOT write assembly code, no matter what cpu are you using. First thing first, macro assemblers have been around for at least 40+ years. So don't use numbers in your code. use macros or defines. Ex. you can comp
30.
by andy_threos_io 6y ago
meanwhile: Dell Precision 7740 with 5 external monitors - 6 screens https://www.youtube.com/watch?v=qrVjjQpzivQ

More ›