Short version:A legacy non-PnP ISA card connected to a LPC ('low pin count') controller appears as 'motherboard resource'.How can I install my KMDF driver for it?2. Long version:A customer has a legacy non-PnP ISA hardware (IO address range=300-31f, and IRQ=5),which is connected through a low pin count (LPC) controller on a special machine controller PC.I have to port my old Compuware/WDM driver to KMDF for that card, because the system should run 64bit Windows now.2.1 approach #1-I constructed a ControlDevice without resource management. KMDF doc says:'Drivers can use control device objects to represent software-only virtual devices orlegacy hardware devices'Access to the IO port range worked, but WdfInterruptCreate failed. No wonder:The WDK-KMDF doc page about 'Creating an Interrupt object' clearly states:'Drivers that do not support Plug and Play cannot use interrupt objects.' 2.2 approach #2-My approach is now to write a full PnP driver. I want to register the ISA resources in such a way, that they are received as regular ResourceLists in the EvtDevicePrepareHardware callback.I got the hint to use 'LogConfig' in the INF file to register the ISA resources to Plug&Play.
![]()
Aug 20, 2018 Stivali Negozio Drivers. Italian blogger, publisher, game dev and social person. This blog he created for sharing drivers with his friends. Totally he did publish 2 million driver files. So no matter what device do you have. You can find its drivers on this blog. Recommend it to all your friends, please.
![]()
You can use wdk interrupts in your kmdf driver by calling IoConnectInterrupt yourself, but think about how you can't handle power in a legacy driver and yet the OS will still need to power down or enter standy or hibernate. Look in%windir%infsetupapi.dev.logfor why the install through device manager did work. I am guessing your driver package was not signed and thus not ranked high enough. This results in an 'CurrentControlSetEnumROOTUnknown' entrywhat command line did you run to get this result?
Devcon install? You need to use devcon update for an existing deviced - This posting is provided 'AS IS' with no warranties, and confers no rights.
You can use wdk interrupts in your kmdf driver by calling IoConnectInterrupt yourself, but think about how you can't handle power in a legacy driver and yet the OS will still need to power down or enter standy or hibernate. Look in%windir%infsetupapi.dev.logfor why the install through device manager did work. I am guessing your driver package was not signed and thus not ranked high enough. This results in an 'CurrentControlSetEnumROOTUnknown' entrywhat command line did you run to get this result? Devcon install? You need to use devcon update for an existing deviced - This posting is provided 'AS IS' with no warranties, and confers no rights.
Hi, thanks for answering. I didn't used devcon so far, because it still has this bug under Win7-32:(switched to a 64bit environent now. (Language is German). I see a bit clearer now: the customer has entered the I/O port range and Interrupt of the ISA card intothe ACPI BIOS tables. Therefore it appears as 'motherboard resource'. I can now install my device driver for the ISA cards. I use 'devcon update' on the ACPI BIOS 'motherboard resource'.
I don't know exactly what I changed.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |