Re: Best way to go about generic driver

2025-02-18 Thread Sebastien Lorquet
Hello, The network interface could have been developed over the generic radio interface I developed to write the char driver. And this network interface would have been generic, so write once, instanciate with all radios. My argument was exactly that network interfaces are overkill and req

Re: Best way to go about generic driver

2025-02-18 Thread raiden00pl
Hi Sebastian, it's a pity that your radio framework didn't go upstream. The lack of a standardized interface for radios is a problem now. Network interface for small radios, especially for LORA radios is overkill. I think Greg later admitted that because he accepted sx127x as a character driver. Th

Re: Best way to go about generic driver

2025-02-13 Thread Sebastien Lorquet
Hello the hardware and driver are cool. However, if this driver is accepted, I will be very mad, as several years ago, I built a complete radio transceiver driver framework based on character devices (for the si4463, using a lower/higher half approach, and it was fully working), and this was

Re: Best way to go about generic driver

2025-02-12 Thread Matteo Golin
I have created an initial RN2XX3 driver here: https://github.com/apache/nuttx/pull/15828 The design was based on some suggestions received on the mailing list earlier in the year. I haven't added quite all of the `ioctl` commands I would like yet, and I want to add some Kconfig options, but I a

Best way to go about generic driver

2025-02-08 Thread Matteo Golin
Hello, InSpace has been working on a driver for the RN2483 radio module. I am also using its sibling, the RN2903, on my flight computer. These chips are almost identical in their interface outside of the some of the available parameters (ex: they both use different frequency bands). I am wonder