Agreed!
I suggested to use the new sensor because it was submitted sometime
ago and I don't see broad adoption.
Maybe it is too much for simple sensors and the fact that there is not
documentation makes things more difficult to digest.
So, I think it shouldn't be a replacement for our previous c
My thoughts: simple things should be simple. Getting temperature or
humidity values from a sensor only requires a few lines of code. A
simple character driver fells just right for me.
More code brings more potential bugs with it. The character drivers
should remain as an option for simple thin
I had a quick skip through the video. My initial thoughts are:
1) This seems to be aimed at multi-sensor, multi-message systems, using uORB;
and, perhaps even, really and perhaps only intended for PX4?
2) is it a "generic" solution, that is a really good idea, and NuttX is right
to be adopting i
On 3/11/23, Xiang Xiao wrote:
> On Sun, Mar 12, 2023 at 12:12 AM Tim Hardisty wrote:
>
>> I submitted a PR for a driver for the Broadcom APDS-9922 ambient light
>> and
>> proximity sensor, written with what one might call the "traditional"
>> method of setting up the device via ioctl, then readi
On Sun, Mar 12, 2023 at 12:12 AM Tim Hardisty wrote:
> I submitted a PR for a driver for the Broadcom APDS-9922 ambient light and
> proximity sensor, written with what one might call the "traditional"
> method of setting up the device via ioctl, then reading data when available
> according to th
I submitted a PR for a driver for the Broadcom APDS-9922 ambient light and
proximity sensor, written with what one might call the "traditional" method of
setting up the device via ioctl, then reading data when available according to
the device setup, via poll notify.
The reviewer (Hi Alan - I'
