Hi... I can only contribute to your 2nd question...
Correct. It's not so obvious when you directly check the macro definition, but after browsing for a while, you will find out that it ends up calling _udelay() or its variant such as _const_udelay().2) AFAIK, mdelay is busy looping, right?
regards, Mulyadi -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [EMAIL PROTECTED] Please read the FAQ at http://kernelnewbies.org/FAQ
