AW: [ros-kernel] CVS Commit: reactos

[Hartmut B. <har...@te...>]

It seems that some programs (gditest) are not able to locate drivers in 
memory. They load the drivers again. See the attached debug output. 
Vidport.sys needs some little changes for runing gditest. One for the dirty 
hack to get csrss's process handle and the other to change interrupt 10h to 
6dh, if loadros is used for booting.

- Hartmut




> -----Ursprungliche Nachricht-----
> Von:	Eric Kohl [SMTP:ek...@rz...]
> Gesendet am:	Montag, 10. Juni 2002 11:05
> An:	ReactOS Kernel
> Betreff:	[ros-kernel] CVS Commit: reactos
>
> ntoskrnl/io/drvlck.c (removed!)
> ntoskrnl/mm/drvlck.c (new!)
> ntoskrnl/makefile
>     Moved driver locking functions.
>
> ntoskrnl/include/internal/io.h
> ntoskrnl/include/internal/ldr.h
> ntoskrnl/io/device.c
> ntoskrnl/io/driver.c (new!)
> ntoskrnl/io/iomgr.c
> ntoskrnl/ke/main.c
> ntoskrnl/ldr/loader.c
> ntoskrnl/makefile
>     Minimize access to the module object via the object manager.
>     Use module list for internal module management.
>     Protect module list with a spinlock.
>
>
> This is the first step of an attempt to reorganize and clean up the 
current
> driver/module chaos. I removed all unneccessary accesses of module 
objects
> via the object manager and replaced them by direct accesses via the 
module
> list.
>
> The next step of the cleanup will replace the current driver objects 
which
> are currently represented by MODULE_OBJECTs by the real DRIVER_OBJECTs.
> MODULE_OBJECTs will only be used as entries of the module list and won't
> appear in the object manager namespace any more.
>
>
> Regards,
> Eric