Hi,
--- Eric Kohl <eric.kohl(a)t-online.de> wrote:
The problem is that Wine needs to use an entirely
different approach
than
ReactOS. We cannot rely on libusb, our configuration manager apis
need to
call to the user-mode-pnp-manager (umpnpmgr.dll) via RPC.
Umpnpmgr.dll
communicates with ntoskrnl via NtPlugPlayControl and
NtGetPlugPlayEvent. As
a short-term sollution we can retrieve some information from the
registry
instead of calling umpnpmgr.
Right I understand. I was hoping we could use libusb as it currently
work on both Windows and Linux but I see what you mean about the
implementation issues...maybe it will still be of help to someone.
Which setupapi functions are needed for this hack?
Right now its a hardcoded hack to SetupDiGetClassDevsA that looks for
the iPods Vendor ID by talking to the /proc filesystem. If it finds the
device it does some other magic to access it. In the future we were
going to add some enumeration for other mass storage devices. I was
hoping we could make it generic enough that ReactOS and Wine could both
use the same code for device identification at least on the userspace
side because if I understand it correctly all USB devices under any OS
use the same ID system. I dont know how the other hardware such as PCI
and friends work.
Anyway there is not much to what we(codeweavers) already have and I
agree I dont think working together on this is going to be much help.
Thanks
Steven
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail