Hello Steve, on 01/27/2012 03:09 PM Steve Sakoman said the following: > On Tue, Jan 24, 2012 at 6:33 AM, Michael Hunold <hunold@xxxxxxxxxxx> wrote: > Your summary below is a pretty accurate description of the current state. Ok. > I've made an attempt at creating a patch for 3.2 that follows David > Vrabel's original patch series as closely as possible with the new > structure. > > Unfortunately it doesn't quite work. I've only been doing this as a > background task so progress is pretty slow. I understand, no problem. > The patch doesn't seem to break support for memory devices (which is > good since my rootfs is on an mmc device!) and I do see SDIO > interrupts occurring and being handled in the debug log, so it is a > good start: > However the SDIO device does not function properly due to multiple > timeout errors, so something is still not quite right. > Let me know if you would like to help with further development of the > patch and I will send you a copy. It is rough enough and broken > enough that it probably isn't yet ready for even an RFC to these > lists. Yes, please send them to me. I will give them a try and let you know the results. As a side node: actually I'm working double tracked. I plan to use it on some OMAP-based board like Beagleboard or Pandaboard for a stationary system, running any kernel that is needed. But I'd like to use some spare N900s as well, because I can carry them around easily. But these are running ancient 2.6.28.1 kernels. David Vrabel mentioned that he originally developed his patches on the N900. I sent him a mail using his mail address from csr.com, but I have not received a reply yet. If you or anybody else has every seen his original patches for the N900 (he did not sent them to any list as far as I know) please let me know as well. > Regards, > Steve CU Michael. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html