On Wednesday 20 April 2005 12.32, Olav Kongas wrote: > I think I'll amend the CLKRDY-triggered error message in the > driver to mention H_WAKEUP as a possible cause.
That was my problem, with the GPIO attached to H_WAKEUP initialized to 0 the test succeeds, thanks Ian. So yes, mentioning this in the driver as a possible cause to this test failing looks like a good idea. Robin ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
