On Mon, 15 Oct 2007, Ingo Molnar wrote:Using emulators to test device drivers is almost certain to be pointless. The problem with device drivers tends to be timing issues, odd hardware interactions, and lots of strange (and sometimes undocumented) behaviour and dependencies (eg things like "you have to wait 50us after setting the reset bit until the hardware has actually reset"). These are all things that you'd generally not catch in emulation - because the emulation by necessity is only going to be a very weak picture of the real thing. So I suspect you can find the easy stuff, but only by writing insanely complex device model descriptions in the emulator environment itself, and only for those device models that have actually been written. Can it be donein theory? Sure. Practically? Not so sure. Would it help? I suspect the effort to do the device model would be many times bigger than *any* conceivable effort to just fix the driver bugs as they get found through other means. So we could perhaps have *really* good emulated hardware for a few models of hw out there, but likely they'd be fewer and less varied platforms than most kernel developers end up having hidden under their desk anyway.. Linus -
| Parag Warudkar | BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 010/196] Chinese: add translation of Codingstyle |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 24/37] dccp: Processing Confirm options |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Alexey Dobriyan | Re: [GIT]: Networking |
| david | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
