> > I think recently some one from TI posted OMAP3 camera driver at > > linux-v4l2 mailing list and which I think was using camera MMU, but > > not the common MMU framework it seems from the description. They > > should first start converting to the common MMU infrastructure then. > > > > http://lists-archives.org/video4linux/23215-omap3-camera-driver.html > > We must make the MMU framework generic for the coprocessors, otherwise > maintenance will be a nightmare and the code will never get merged > upstream. Main issues are at outer interfaces which deal with OS memory system interaction. The other aspects of the code have been self contained. The local MMU usages are not maintenance intensive like linux PTE structures as Linux more strongly couples with the hardware table representations. Seems some of the subsystems like v4l2 do provide local abstractions but there isn't always global ones (vmalloc to sg list for example). Seems main benefit would be if there were common map conversion and flushing code. Regards, Richard W. -- 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
