**** BEGIN LOGGING AT Thu Mar 05 02:59:57 2020
Mar 05 19:36:48 <ymdatta> Hey ds2 , i am interested in working on 'mikroBus driver' project, i had some doubts and they were clarified by Abhishek
Mar 05 19:37:08 <ymdatta>  * Hey ds2 , i am interested in working on 'mikroBus driver' project, i had some doubts and they were clarified by Abhishek_
Mar 05 19:37:20 <ymdatta> Here is what i understood about the project:
Mar 05 19:37:29 <ymdatta> There can be a lot of MikroBus sockets on the mainboard, we can test an add-on board(clickboard),
Mar 05 19:37:29 <ymdatta> remove it and test another.
Mar 05 19:37:50 <ymdatta> This makes the sockets highly configurable. Rebooting the main board each time when we change
Mar 05 19:37:50 <ymdatta> add-on board so that newly added add-on board will get picket up by the kernel defeats the
Mar 05 19:37:50 <ymdatta> purpose of the board being highly configurable.
Mar 05 19:37:57 <ymdatta> So, instead of getting the information about the board from the device tree, we want to get the information out of the tree via I2C.
Mar 05 19:38:06 <ymdatta> The goal of the project is to implement the driver which does the above.
Mar 05 19:38:18 <ymdatta> Is my understanding of the project correct (or) am i missing something?
Mar 05 19:38:30 <ymdatta> What should be my next step of action? should i start preparing a proposal? can you please point me what i can do further?
Mar 05 19:39:39 <ymdatta> I have background in kernel development and device drivers.
Mar 05 23:39:42 <pradan[m]> @ds2
Mar 05 23:39:42 <pradan[m]> Hello Sir,
Mar 05 23:39:42 <pradan[m]> You referred to the YOLO models already tested on the x15 using the convolution method which gave the latency to be around 10s. In this, what was the method of testing your model?
Mar 05 23:40:48 <pradan[m]> I mean, was it directly on the x15 board or was it cross compiled locally....
**** ENDING LOGGING AT Fri Mar 06 03:00:02 2020