Hi Khasim, On Fri, Aug 15, 2008 at 11:02 PM, Syed Mohammed, Khasim <khasim@xxxxxx> wrote: >> >> Really all the design, maintenance and test experience of that code is inside of TI. This has lived >> for years and derivates have shipped in products. Who ever watches over it needs to be able to >> provide a creditable multi-year commitment. >> > <snip> > > Just to add few points, > > As we know the OMAP3530 (having same DSP as 3430) processor _today_ supports DSP Link / CE for ARM-DSP communications. Link/CE is extensively used in Davinci family of processors and has been continued on OMAP3530 as well. > Oh..so you are saying that DSPBridge is going to be deprecated going on and DSPLink will be used? It beats me that why anyone would go for two separate bridges one for OMAP3 and another for DaVinci, and now you are mentioning that OMAP3530 will go for DSP-Link instead of DSPBridge. It is just confusing. > Moving forward we should also see a common set of API framework evolving for users of Link and Bridge to leverage applications developed for different domains. > I wish that DSPBridge and DSPLink/CE would kill each other in fight and hope new winner will emerge dspfs-no-bridge-no-link but only communication :) > We also have DSP gateway on our tree today which is used to some extent but might be deprecated in future. > I hope you mean Nokia DSPGateWay. > So, a maintainer needs to know past, present and future work that is going to happen for DSP software development in >coming months. With multiple open platforms on OMAP, I think we will see a good amount of traffic for OMAP and DSP in >particular. Yes and No, as far as TI is ready to support him. -- ---Trilok Soni http://triloksoni.wordpress.com http://www.linkedin.com/in/triloksoni -- 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
