david-vankampen

Note that you can also use the output of `bear` as a comparison, as follows: ```bash bear make # build output... ❯ jq -r '[.[]] | length' compile_commands.json 144 ❯...

@maribu - you did some of the work on the compile-commands target. Any thoughts here? We're currently wrapping our build with `bear` but would prefer to be able to omit...

Thinking out loud - could one solution be the option for a package to "register" or provide some hooks into the RIOT build system? It wouldn't cover all packages, of...

@benpicco from the reference manual:  this allows the MCU to interact with an RS-485 transceiver like [this TI chip ](https://www.ti.com/document-viewer/THVD1439/datasheet/GUID-9D11057E-F990-4E6A-990B-E0FA0B3DAD9A#TITLE-SLLF79X3399) - the DE and RE inputs there can be...

@benpicco with the updates I just pushed, if I run the following command on `tests/periph_uart`: `FEATURES_REQUIRED=periph_uart_rs485 make BOARD=nucleo-g070rb`, and then use `arm-none-eabi-objdump` to check for the conditional code, I see...

@benpicco checking in - is anything still needed here?

Added it to `tests/periph_uart`. and yes, the DE pin is enough to get the MCU communicating on RS-485, as long as it is routed to an RS485 transceiver, as linked...

@fjmolinas hows that?

> I think this PKG could be integrated into the existing ws281x driver as an alternative backend. See https://api.riot-os.org/group__drivers__ws281x.html @maribu to be clear, are you thinking keep the package, and...

That makes sense. So I think I will leave it in as a pkg, but then add the needful references to that package to the ws281x driver. That way if...