Why would anybody want to simulate hardware when developing a device driver? This linux-based article lays out the problem and proposes an approach to solve it. Part 2 of this two-part series, “Debugging simulated hardware on Linux, Part 2: Device driver debugging.” gives you a strategy for debugging the complete code flow of your drivers.
Easing Device Driver Development
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
Perhaps they should share with developers the ugly side of Linux driver development: Your driver will be guaranteed broken in (at most) 6 months. You can thank the kernel developers for releasing kernels that break your binary drivers on a regular basis.
Ladies and Gentlemen! Start your simulated GPU’s!
Why would anybody want to simulate hardware when developing a device driver?
That’s a trick question, isn’t it? I mean, who wouldn’t want to simulate hardware when developing a device driver?!?
What he’s talking about is normal-practice… anybody who has developed drivers for any type of new hardware uses simulation techniques for development and debugging.
This is only the exception when creating linux drivers when the driver is written AFTER the hardware has been developed.
Some news I can use, thanks.