On Sat, Sep 13, 2014 at 5:10 PM, Michael M <[email protected]> wrote: > I believe that PRUSpeak(https://github.com/deepakkarki/pruspeak/) makes use > of remoteproc. I haven't made the transition yet, but I'm definitely curious > about it. The complexity of implementing remoteproc seems much, much greater > than using UIO or /dev/mem mapping. What is the benefit of using remoteproc > over the other methods?
I'm not sure of all the advantages, but here are some: * The more "Linux" way to do it with the remote processor being abstracted as a processor and not just some random memory mapped thing * Uses the kernel firmware loader making managing firmware something that can be easily coupled with the kernel and standard file formats * Processor-agnostic communication abstractions such that "platform-specific remoteproc drivers only need to provide a few low-level handlers, and then all rpmsg drivers will then just work"[1] * From a performance perspective, it enables handing of remote processor events from the kernel level which avoids a userspace context switch * Vring communication can be rather efficient as seen in the case of BeagleLogic [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/remoteproc.txt > > > On Friday, September 12, 2014 5:57:17 AM UTC-7, Cedric Malitte wrote: >> >> >> >> Le vendredi 12 septembre 2014 04:11:18 UTC-4, Jon E a écrit : >>> >>> Hi, >>> >>> Anyone know of example code that's using the newer remoteproc interface? >>> Also, is there a way to convert pasm binary files to elf format for the >>> firmware loader? >>> >>> Would like to play around with the latest 3.14 TI kernel, but haven't >>> been able to find much info on the PRU side.. >>> >>> Thanks, >>> Jon >>> >> As I read here >> http://processors.wiki.ti.com/index.php/PRU-ICSS_Getting_Started_Guide >> There are some examples included in the SDK. >> >> I'm downloading it to check that, but for now i'm still using the old >> patch method to enable pruss :) >> >> Regards, >> Cedric > > -- > 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 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.
