On Tue, 2011-06-21 at 12:35 -0400, Preeti Sharma wrote:
> I am running openhpid in gdb. I set break point at oh_process_events
> (this method is called in oh_evtpop_thread loop). I ran client
> hpipower to generate event once openhpid initialization and discovery
> completed. I am not seeing any hit to my break point. I see hit to
> this break point only during discovery. Hope this is safe for me to
> comment out oh_evtget_thread_loop creation to reduce processing load.
> I am as well interested to comment out oh_evtpop_thread loop (if it is
> not needed). As well, why we should have discovery thread running
> after every 3 minute (once initialization of plugins is complete), it
> is to handle clients' saHpiDiscover calls?

I would encourage you to try all these things.  If it works for you,
then that's great.  If it doesn't work, you can put the code back in.

The wonderful thing about open source code is that you get to see it,
modify it, and "make it your own".  If it doesn't do exactly what you
want it to, please modify it to suit your own needs.  However, if it
doesn't work after you modify it, you will need to make it work
yourself.

> As well I am eager to know out of 5 threads which threads are per OA
> basis.

There is no current documentation for this question.  However, please
review the source code.  I am sure the answer can be found there.

Preeti, HP and other companies have invested substantial engineering
efforts into making OpenHPI work with their hardware products.  In
addition, they have done this within an open source project, so that you
can have complete access to the source code, learn from it, and modify
it for your specific needs.  As you do this, please remember that there
is no promise of support for this free software.

Best regards,
Bryan Sutula


------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to