Cameron, can you take a look at https://jira.reactos.org/browse/CORE-8292 ? This describe the problem occured with the "on-the-fly load driver" that we need
Thanks (Cameron Gutman <aicomman...@gmail.com>) Tue, 13 May 2014 15:29:47 -0500: > InitializeHandler is called when the miniport is started by the PnP > Manager. You can't force a miniport driver to be loaded without a device > (whether real or virtual) for the miniport driver to control. > > You'll want to just create an INF file that installs your miniport driver > for some PnP ID that you make up. You can then call some SetupAPI functions > to create a virtual device node and install your driver on it. > > Here's an example of what you'll want to do to create the virtual device: > https://github.com/CrowdStrike/Tortilla/blob/master/Tortilla/InstallTortillaDriver/InstallTortillaDriver.cppon > lines 635-811 > And here's an example of the INF you'll need to write: > https://github.com/CrowdStrike/Tortilla/blob/master/Tortilla/TortillaAdapter/netTor.inf > > I don't know whether this will work on ReactOS. The code seems to be there, > but that's no guarantee that it works ;) > > Thanks, > Cameron > > > On Tue, May 13, 2014 at 3:15 PM, Maxime Daniel <l...@maxux.net> wrote: > > > In fact, we the problem we face is the Miniport Initialize function which > > seems to be ignored when using Virtual Ethernet (without hardware). This > > problem seems linked with PnP Manager. > > > > In this version: > > http://git.reactos.org/?p=reactos.git;a=blob;f=reactos/drivers/net/ndis/ndis/miniport.c;h=399ff1cb97546d9f0a43bb1c2a698ee831e3983b;hb=e3cbb33ea64b0bd3f56767dc397500ed6bb38e16 > > The InitializeHandler is hard-called on the end of NdisMRegisterMiniport. > > > > On the current implementation, the single time InitializeHandler is called > > is on NdisIPnPStartDevice. How the PnP Manager can be called by another > > driver to load it manually ? What should be done or edited to make it > > possible ? > > > > Thanks > > > > (Aleksey Bragin <alek...@reactos.org>) Thu, 08 May 2014 21:35:14 +0400: > > > > > Guys, any ideas? > > > Cameron, maybe you could tell what direction to look? > > > > > > This blocks further work in the area. > > > > > > Regards, > > > Aleksey Bragin > > > > > > On 08.05.2014 19:15, Maxime Daniel wrote: > > > > Hi, > > > > > > > > I'm working on network virtualization support in ReactOS. > > > > At this time, PoC works but I reach a point where I need a solution > > that would allow to add and remove TAP (TAP-Win32 from OpenVPN for exemple) > > Network Devices from kernel space, without user intervention. > > > > > > > > The problem right now is that there seems to be impossible in ReactOS > > to have a proper way or tips and tricks to add/remove TAP devices without > > rebooting the system. What should be fixed/edit to instanciate of TAP > > device on the fly on the current implementation (r63193) ? > > > > > > > > Thanks > > > > > > > > > > > > > _______________________________________________ > > > Ros-dev mailing list > > > Ros-dev@reactos.org > > > http://www.reactos.org/mailman/listinfo/ros-dev > > > > > > -- > > Daniel Maxime > > Linux version 3.10.9-maxux64 (syna) (gcc version 4.7.3 (Gentoo 4.7.3 p1.2, > > pie-0.5.5) ) #6 SMP Thu Sep 5 20:17:50 CEST 2013 > > 22:06:43 up 17 days, 21:25, 8 users, load average: 0.22, 0.36, 0.34 > > > > _______________________________________________ > > Ros-dev mailing list > > Ros-dev@reactos.org > > http://www.reactos.org/mailman/listinfo/ros-dev > > -- Daniel Maxime Linux version 3.10.9-maxux64 (syna) (gcc version 4.7.3 (Gentoo 4.7.3 p1.2, pie-0.5.5) ) #6 SMP Thu Sep 5 20:17:50 CEST 2013 15:44:54 up 40 days, 15:03, 16 users, load average: 0.30, 0.35, 0.39 _______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
