Thread: [Ndiswrapper-general] Ndiswrapper for non-network miniport drivers?
Status: Beta
Brought to you by:
pgiri
From: Jelle F. <jel...@fo...> - 2003-12-03 22:45:58
|
Hello, I'm just wondering, would it be possible to use ndiswrapper for non network drivers? I'm not really into windows drivers, but if I understand correctly, there is something called a 'miniport' driver. I have a nice video grabber card with MPEG2 encoder (creative sb dvcr), that I would like to get working under Linux. It only comes with a windows driver and much too little information about the chips to make a native driver... But I think that the low level driver for the card is a video 'miniport' driver, and my hope is that there are some similarities to an ndis driver? Something like a dll that has to be loaded, and then there is an entry point that allows the various functions to be called? Can anybody who knows a bit more about windows drivers elaborate? Or maybe point me towards more detailed info about miniport (specifically video input) drivers? Jelle |
From: Pontus F. <pon...@ta...> - 2003-12-04 11:22:32
|
On Wed, 2003-12-03 at 23:45, Jelle Foks wrote: > Hello, > > I'm just wondering, would it be possible to use ndiswrapper for non > network drivers? No, but the GPL gives you the freedom to for example use the windows exe-loader from our project. Pontus |
From: Stefan <ste...@gm...> - 2003-12-04 14:40:23
|
Hello, > I'm just wondering, would it be possible to use ndiswrapper for non > network drivers? I fear not. Generally everthing is possible, but you have to implement the API the drivers use. That's exactly what we do here, but we only implement the API functions needed for Ndis drivers. If you want to get your mpeg card running it's probably better to s.tart a new project. In your case it's probably easier to ask the vendor for specs. Or just have a look around in the internet, maybe you can find a driver. It could also be that the card can be used by a standard driver but your distro just doesn't know about it. The miniport drivers are because the card's drivers consist of a big general driver(included in windows) and a relativly small miniport driver which handles special functions of the card. I read this a few years ago and I hope it is still correct for today's Windows versions. /Stefan |