On Tue, Oct 5, 2010 at 10:07 PM, Greg KH <greg@xxxxxxxxx> wrote: > On Mon, Oct 04, 2010 at 07:09:13PM +0300, Felipe Contreras wrote: >> It seems the platform device was dropped from the migration of tidspbridge into >> staging, plus the sdram meblock (previously bootmem) required for it work are >> gone. >> >> Withouth these patches the driver loads, but doesn't do anything. >> >> A second issue with ioremap() still remains, but that can be solved by >> reverting 309caa9. >> >> I think these might be worth to get into 2.6.36, if not, I have versions with >> more changes; cleanups and so on. > > I've applied this to my staging-next tree, for .37, as it's not a big > deal for .36. Well, I thought it would be nice if the driver actually worked on .36, but anyway, I'll rebase the rest of my cleanup patches and send them. Hopefully I find a way to get rid of the ioremap() issue. Cheers. -- Felipe Contreras -- 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
