My problem is with some discrepancy between the SA-HPI standard and the OpenHPI
implementation regarding the OpenSession() API:
According to the standard, this API should be handled by the SA-HPI
implementation (i.e. OpenHPI), and need not go down to the level of the plug-in
(loaded by OpenHPI).
However, when looking at the implementation, we see that whenever OpenSession()
is called, it is translated at the end of the flow to some function call to the
plug-in layer.
This imposes some complex implementation on the HW plug-in (i.e. creating
dedicated event queue for each session opened, and sending notifications to all
of these queues for each HW event).
I was wondering whether we have some misunderstanding of the Standard, or
whether our understanding of the plug-in responsibility and implementation is
wrong.
Basically, if we can get some answers and clarifications of what is required
from the plug-in in order to implement multiple sessions, and if multiple
sessions are a must from OpenHPI POV (if not, what is the preferred way to use
it).
Thanks,
Ron Savir
SW Engineer, hiD6680 Project, R&D
3 Hanagar St. Neve Ne'eman B
Hod Hasharon, Israel
Tel: +972-9-775-1631
Mob: +972-54-5524824
[EMAIL PROTECTED]
http://www.nokiasiemensnetworks.com/global/
Think before you print
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
