acassis commented on PR #12829:
URL: https://github.com/apache/nuttx/pull/12829#issuecomment-2271474227

   > @acassis @xiaoxiang781216 I need your help again. My understanding is that 
:
   > 
   >     * the **fb.c** holds the framebuffer character driver, can be used to 
interact with displays, or with a image.
   > 
   >     * I would need to make my sensor "compatible" with v4l2 (interaction 
with the my senzor should be done through v4l2)
   >       Now the things that I do not understand:
   > 
   >     * That is goldfish_*.c, my guess is that is is an driver used with 
qemu (pipe or brige or something),
   > 
   >     * I see that isx012 and isx019 camera drivers both uses imgdata.h and 
imgsensor.h
   > 
   > 
   > My main issue, is that I'm not sure about the flow of data from sensor -> 
driver code -> v4l2 -> userspace. What is the link between them. Now I've read 
anything I could about this topics but there is not too much documentation on 
nuttx side. Could any or you help me with a short description of how the date 
should get from sensor to userspace?
   
   Hi @LuchianMihai, I'm not an expert on that subject but I think you just 
need to implement a imgsensor like those existing at drivers/video/ and 
v4l2_cap.c will use it.
   
   You are completely right, although NuttX uses V4L2 and the API from Linux 
could help, we still need some documentation explaining how things connect on 
NuttX side. This is something I try to enforce during to PR reviews: we need 
Documentation/ otherwise people will spend a lot of time trying to figure it 
out.
   
   Maybe @xiaoxiang781216 or someone from Xiaomi or Sony could help here, 
because they contributed the code.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to