2012/2/15 Víctor M. Jáquez L. <vjaquez@xxxxxxxxxx>: > On Tue, Feb 14, 2012 at 08:56:11PM -0600, Ramirez Luna, Omar wrote: >> On Tue, Feb 14, 2012 at 10:23 AM, Felipe Contreras >> <felipe.contreras@xxxxxxxxx> wrote: >> >> When that case is applicable, we should first modify the loader code >> >> or prepare the baseimages to be common so we can get rid of specific >> >> loaders and just dump them into memory. >> > >> > I'd say the less workarounds, the better. >> >> If there are ever more base images compatible with the dsp, I would >> say that unifying them into a common format to be dumped in memory >> isn't a workaround, and in that process we can get rid of the custom >> loader code. > > Yes! please! and use Ohad's rproc thingy. Yes it would be nice, in theory we could replace some parts with remoteproc maybe not the loader yet, not sure how much rpmsg will fit. > What would be the steps to unify that common format? I guess we will depend on > TI for that... Do we? I don't know the stance of TI on this. But basically we have a loader in kernel space that prepares the baseimage to be dumped in memory, that can be done in user space or better to distribute a baseimage that just needs to be dumped in memory, however there might be some constraints that need to be solved like the tight coupling between the driver and the loader, the current format of the base image, the size and how it expands to fit in the 6MB of shm, and so on, not to mention the ability to load dynamic code. I guess it would be better to dive in the code and see. Regards, Omar -- 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
