On Friday 25 February 2005 21.54, Olav Kongas wrote: > Always great to get success reports, thanks :) Yet bugs get > fixed only if people report them.
Yeah sure, but I really thought the problem came from the hardware only and I was trying to better understand it before reporting hypothetical bugs :). > Could you please elaborate on the problem of failing clock > checks? Can this be a driver problem? Or hardware problem? During the chip initialisation, your driver polls the ClkReady bit in Hc�PInterrupt for a few milliseconds and if the bit is not set during this interval, the driver reports an error and stops there. I guess this check is working for you and since there is no black magic here, it has to fail due to a hardware problem. Robin ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
