3 ms·
hm, I dont feel the same way you should do some coding closer to the chip some bitshifting, some bit level manipulation you dont have to be good at assembly,
by yieldcrv 3y ago
hm, I dont feel the same way
you should do some coding closer to the chip
some bitshifting, some bit level manipulation
you dont have to be good at assembly, just do a hello world and make a mental visualization of the registers being hit
look up the OPCODES in your specific chipset , make some code to hit that specifically
make a process that does it as fast as possible and benchmark it, do it faster or slower on a different chipset, or a resource constrained environment
it makes it all really easy to follow and visualize
- kccqzy 3y agoThat's not even close to the chip. Dabbling around with the ISA doesn't tell you much about the micro architectural features of the chip. I'm sure "do some bit twiddling" is absurd advice for someone who has written a driver.
- yieldcrv 3y agois all of it absurd advice? its about breaking abstract problems into smaller digestible problems to get a mental map I dont think you need to write a driver for that map
- rwmj 3y agoBetter advice would be to look at some of the open source RISC-V cores. They are nowhere near as complex as Apple's Axx silicon (probably not even 0.1%) but they demonstrate at least some of what goes on at the lower levels.