New #RISCV hardware designs for #5G
https://arstechnica.com/gadgets/2021/01/new-risc-v-hardware-designs-from-5g-startup-edgeq/
Unsafe #RustLang: How and when (not) to use it
https://blog.logrocket.com/unsafe-rust-how-and-when-not-to-use-it/
Hacking your #Nissan Car
The Assignment looks odd because "pstmsg->event" has already been set by the calling function "i2c_interrupt_entry" ... And "pstmsg->event" isn't used after "i2c_transferbytes" returns to "i2c_interrupt_entry" 🤔
We have created an issue for this...
https://github.com/bouffalolab/bl_iot_sdk/issues/33
Convert your Windows install into a VM on #Linux
https://opensource.com/article/21/1/virtualbox-windows-linux
@lupyuen @chrysn
Yeah, it probably should be a "==", although I've often seen guys take advantage of the way "AND" conditionals are processed in order to assign variables (if the first condition is in not true, it won't bother to execute the second test and so the variable won't get assigned, but if the first condition is true the variable is assigned. It's bad form but seems to be accepted practice in some scripting languages.
@lupyuen Unless the right side is secretly a variable: because someone has been developing in C in hubris mode (aka "I don't need fatal warnings, I know what I'm doing").
#BL602 I2C has a FIFO Queue of 4 bytes ... Here's how we transmit and receive I2C data in chunks ... On #PineCone @PINE64
https://lupyuen.github.io/articles/i2c#transmit-and-receive-i2c-data
#BL602 I2C HAL looks a little dubious... Why is there an Assignment inside a Condition? 🤔
https://github.com/bouffalolab/bl_iot_sdk/blob/master/components/hal_drv/bl602_hal/hal_i2c.c#L74-L95
#BL602 I2C Interrupts ... How we handle them on #PineCone and #Pinenut @PINE64
https://lupyuen.github.io/articles/i2c#handle-i2c-interrupts
IoT Techie and Educator / Apache NuttX PMC