On Wed, Aug 25, 2010 at 10:42 PM, Guzman Lugo, Fernando <fernando.lugo@xxxxxx> wrote: >> On Wed, Aug 25, 2010 at 7:00 PM, Guzman Lugo, Fernando >> <fernando.lugo@xxxxxx> wrote: >> >> Or the whole iovmm.c can be copied and just remove the mapping. >> > >> > That is the migration patches do, remove custom bridge >> mapping and use >> > iovmm module instead. >> >> You didn't get me; copy the iovmm.c code into dmm.c, and >> remove the mapping. > > It sounds like double work, changing the dmm.c which will disappear. But in the meantime the bug is still there, and there's no timeline when it will disappear. > Also I think what you want is only the change from array to > Linked list. That's what I said. > Otherwise copying iovmm.c into dmm.c and adapting > To how dspbridge is at this momment it will need too much changes, Yeah, I just said that it was possible. > It is better to think like: take memory reservation (linked list) > Implementation from iovmm and map it to dmm.c. I think so too. > But I don't see the point of doing that, if dmm.c is about to > Dissapear. When exactly? -- 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
