WINDOWS KERNEL DRIVER FOR DEVICE POWER MANAGEMENT (III)

PLEASE ONLY BID IF YOU HAVE WINDOWS KERNEL/DRIVER DEVELOPMENT EXPERIENCE.
BIDS RECIEVED WITHIN 5 MINUTES OF POSTING WILL BE IGNORED BECAUSE IT MEANS YOU HAVE NOT READ THE SPEC.
WHEN BIDDING PLEASE CONFIRM YOU HAVE READ THE SPEC BELOW.
We are seeking a driver developer to work on a small Windows kernel-mode driver.
We think this could be implemented as a virtual HID driver (e.
.
keyboard).
However, this is only one approach and we are open to alternative implementations.
The driver should provide an IOCTL based interface that delivers the following features.
1.
Wake system from standby state.
a.
Wake in future (required for S1-S4) e.
.
wake in specified number of seconds b.
Wake immediately (required for "modern standby") c.
Optionally, wake-up should simulate user presence e.
.
simulated key press or similar d.
Cancel pending wake request NB.
We require the driver to wake from the hibernate, sleep and "modern standby" states.
2.
Initiate sleep e.
.
modern standby or S1-S4 3.
Report power state transitions from kernel to user mode using inverted call mechanism or similar e.
.
Sleeping, resuming, shutting down and if possible, report if user was present via an inverted call mechanism or similar.
Other requirements.
1.
The driver should support Windows .
The driver should be as simple (minimal) as possible 3.
The driver should be written in C/C++, ideally using the KMDF framework 4.
The project should include user mode code to detect, install and remove the driver (we can provide example code) 5.
The project should include user mode example code to communicate with the driver 6.
The project should provide full source code on payment for each milestone 7.
The project will be broken down into (at least) 3 milestones for the features above and shall only proceed to the next milestone upon satisfactory completion of the previous milestone and provision of working source code.
8.
Please don't bid if you do not have previous kernel mode development experience or do not have a device that supports modern standby or "Standby (S0 Low Power Idle)".
This can be verified with POWERCFG /A.
9.
If necessary, the developer should provide brief technical instructions to install/remove the driver and any other information required to complete the tests below.
The driver can be test signed and tested on a system with test signing enabled.
10.
We can provide user mode code to demonstrate entering hibernate / sleep and scheduled wake-up.
This code is only an example and does not support modern standby (which we think must be done in kernel mode).
The acceptance criteria for the milestones is as follows.
1.
Wake system from standby state.
a.
Confirm device supports modern standby.
POWERCFG /A b.
Configure device to wake in 60 seconds c.
Manually sleep device (via Start Menu/Sleep) d.
Wait ~60 seconds and confirm device wakes AND screen turns on (indicating user presence) e.
Repeat for sleep and hibernate modes (may require alternative device) f.
Repeat above but cancel wake request.
Confirm device does not wake-up 2.
Initiate sleep e.
.
modern standby or S1-S4 a.
Confirm device can enter modern standby "Standby (S0 Low Power Idle)" on demand using supplied software b.
Confirm device can enter sleep (S1-S3) on demand c.
Confirm device can enter hibernate (S4) on demand 3.
Report power state transitions from kernel to user mode using inverted call mechanism a.
Confirm tests for milestone 2 are accurately reported to user mode application Programação C Programação C++ Arquitetura de software Área de trabalho do Windows ID do Projeto.
# Sobre o projeto 17 propostas Aberto para ofertas Projeto remoto Ativo em 19 minutos atrás