I don't think there's anything you could do. If the SD driver was open, you could cluster it with printk's to see what's exactly happening, but unfortunately this is not an option. I believe the root of all problems is that Sharp optimized their ROM (including kernel and all apps) to enforce and probably rely on a certain timing, which we can't reproduce since we want to use newer apps on OZ.
