On Feb 24, 2011, at 12:15 PM, Chris Ball wrote: > On Thu, Feb 24, 2011 at 10:32:30AM -0800, Philip Rakity wrote: >> proposed this a while ago and strongly support just removing the quirk for >> broken timeout and setting the timeout value to maximum of 0xE. >> >> This also handles the case of the sd device having a timeout value too low. >> In my testing I have come across SD cards that do not provide the correct >> value. >> We force our pxa168, pxa910, and mmp2 controllers to have 0xE. > > Yeah, OLPC's CaFe controller -- which might be the same hardware as yours, > actually -- has the same problem.
different controller not same as on mmp2, pxa168, pxa910 > > Does anyone know of a reason (beyond strict spec-compliance, I suppose) > for honoring the timeout value rather than using 0xE everywhere? If not, > I'm willing to try out Philip's suggestion. > > Thanks, > > -- > Chris Ball <c...@laptop.org> <http://printf.net/> > One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
