Look at the recently submited mail box subsystem. Le 10 nov. 2014 21:25, "John Syn" <[email protected]> a écrit :
> > On 11/10/14, 10:58 AM, "Nishanth Menon" <[email protected]> wrote: > > >On Mon, Nov 10, 2014 at 11:54 AM, John Syn <[email protected]> wrote: > >> > >> On 11/10/14, 1:15 AM, "Jason Kridner" <[email protected]> wrote: > >> > >>>On Sun, Nov 9, 2014 at 1:13 AM, Maxim Podbereznyy <[email protected]> > >>>wrote: > >>>> John Syn, > >>>> Wandboard Quad does have 64 bit memory bus. > >>>> > >>>> P.S. I don't know who needs dual DSP onboard because TI definitely > >>>>will > >>>>not > >>>> support them as should like it was for omap3/dm37. I'd better have > >>>>well > >>>> supported hardware video encoder/decoder rather than double general > >>>>purpose > >>>> DSPs without any software support > >>> > >>>When OMAP3 came out, the only compilers for C6000 were expensive, > >>>closed-source compilers. Now, there is support in mainline GCC for > >>>C6000. As the BeagleBoard.org community, we have to work together to > >>>enable use of the DSPs if they are of interest to the > >>>community---there aren't any barriers in our way. > >> The TI C6000 does some amazing pipeline optimization, which seems to be > >> missing from the GCC compiler. Anyway, using CCSV6 is no big deal, but > >> support for RPMSG/REMOTEPROC on this processor is a big issue. The > >>source > >> is difficult to follow and my guess is we would need input from the > >> original authors to do this work. > > > >Why dont we get involved in linux-omap discussions on the topic? most > >of the rpmsg and remote proc discussions do take place in kernel > >mailing list. usually discussing in context helps move patches forward > >since it makes it clear to certain maintainers that these things are > >important and help community. > > > > > >Do you have anything specific that you are concerned about? > Looking at git.ti.com/rpmsg/rpmsg, I don¹t see any support for AM572x > processors. Also, Beagleboard-X15 is to be released with Kernel V3.18 but > I don¹t see support for this kernel versions. Last I heard, RPMSG was > working on OMAP4, but not fully implemented on OMAP5, but this was a while > ago and perhaps this has changed. Perhaps Suman can give us an update. > Similar concerns about REMOTEPROC. What I know is that I have been pushing > this issue on the beta list and the only feedback I received was that > "RPMSG/REMOTEPROC was in a SW blackhole². > > Based on the TRM, this processor looks extremely attractive, and we need > RPMSG/REMOTEPROC to take advantage of the powerful dual DSPs and dual > CortexM4s. > > Regards, > John > > > >-- > >--- > >Regards, > >Nishanth Menon > > > >-- > >For more options, visit http://beagleboard.org/discuss > >--- > >You received this message because you are subscribed to the Google Groups > >"BeagleBoard" group. > >To unsubscribe from this group and stop receiving emails from it, send an > >email to [email protected]. > >For more options, visit https://groups.google.com/d/optout. > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/1t3yxkPYSB8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
