Hi,
I would like to know about what is required for the irp framework to be implemented for wine. I just want to put enough information so that it might be possible for someone or even me to pick-up this issue. May be this might be ready for the next years Google SOC. ;)
Thanks, Vijay
On 30/04/06, Vijay Kiran Kamuju infyquest@gmail.com wrote:
Hi,
I would like to know about what is required for the irp framework to be implemented for wine.
Well we never actually wrote a real irp queue system, we simply had a single irp stack allocated irp struct that we recycled for each call. The whole thing works quite well, the only real issue is that Alexandre decided last December he didn't like the idea of using named pipes for ntdll to ntoskrnl IPC (ntosknrl runs as an independent process), and wanted the whole thing rewritten using the wineserver portocol, which is sort of time consuming and I won't be able to do it before summer. If you want to look over it I can send you what we currently have.
Ivan.
We might put some initial effort, so that when more hands will make it faster. Im quite illiterate with Win32 API, but i might look into your effort and make some changes.
Thanks, Vijay
On 4/30/06, ivanleo@gmail.com ivanleo@gmail.com wrote:
On 30/04/06, Vijay Kiran Kamuju infyquest@gmail.com wrote:
Hi,
I would like to know about what is required for the irp framework to be implemented for wine.
Well we never actually wrote a real irp queue system, we simply had a single irp stack allocated irp struct that we recycled for each call. The whole thing works quite well, the only real issue is that Alexandre decided last December he didn't like the idea of using named pipes for ntdll to ntoskrnl IPC (ntosknrl runs as an independent process), and wanted the whole thing rewritten using the wineserver portocol, which is sort of time consuming and I won't be able to do it before summer. If you want to look over it I can send you what we currently have.
Ivan.
-
ivanleo＠gmail.com -
Vijay Kiran Kamuju