**** BEGIN LOGGING AT Sun Aug 18 02:59:57 2019
Aug 18 09:11:56 <pratimugale[m]> zeekhuge Abhishek_ Could you please have a look at the documentation at https://github.com/pratimugale/PRUSS-Bindings/wiki and provide feedback/changes required in it
Aug 18 09:17:00 <pratimugale[m]> All the firmware examples now use the pruss_api driver and I have tested them again, the documentation for some of the examples needs to be updated.
Aug 18 14:41:47 <pratimugale[m]> zeekhuge There were two small bugs which I solved here: https://github.com/pratimugale/PRUSS-Bindings/pull/31/. So all functions from prussd.py and pruss.cpp are in a working state now.
Aug 18 14:47:36 <pratimugale[m]> There bugs were in the load() and showRegs() functions; load() wasn't working and showRegs() was causing an issue due to a buffer size limit  while receiving from /tmp/prussd.sock
Aug 18 14:57:04 <zeekhuge[m]> Sounds nice.
Aug 18 14:57:16 <zeekhuge[m]> Haven't looked into the link. Will do tonight.
Aug 18 15:15:02 <pratimugale[m]> ok, thanks
Aug 18 21:23:40 <embden_new[m]> julieng:  drhunter  sstabellini  it is quite hard to understand on what to work. I started to think on how to tidy up the code and found that it is quite hard to do it right. My naive implementation when I check whether the node is crossbar in the domain_build.c smells not good. So, I am wondering what is the best way of implementing it? Tegra's implementation is much better but still doesn't look elegant.
Aug 18 21:23:58 <embden_new[m]> https://lists.xenproject.org/archives/html/xen-devel/2017-04/msg00991.html tegra implementation of legacy intc support
**** BEGIN LOGGING AT Sun Aug 18 22:17:39 2019
**** ENDING LOGGING AT Mon Aug 19 02:59:57 2019