> > *Thanks, that appears to be a pretty small patch, I'll try it out.* > *I would have no problem using the remoteproc_pruss if it was in the > official kernel but I can't see any as of 4.6-rc4.* >
The main problem I see with remoteproc is that it is not as well documented as uio_pruss. Many aspects of how to use, and setup remoteproc are not very clear. For instance, you have these magic "map" files that I have been able to find zero documentation on. Which is in relation to configuration for PRUs as far as I can tell. .bss, data segments, etc, but it's not documented at all. So we're left to assume we know what we're doing. I personally, do not like to operate like that at all. I had someone on this group tell me not long ago that I must be joking when I tried to explain I was note sure how something worked with remoteproc on the PRU's. But see that the problem when you're dealing with someone whose known the secrete handshake for a long enough period of time that they forget the rest of the world doesn't know what's going on. Anyway, uio_pruss has been around long enough to have worked well on the white, and the driver code is really short and easy to read through. Not to mention that UIO is just really cool technology to begin with. remoteproc is really cool technology too as far as I'm concerned, but where it really belongs in my personal opinion, is multi core application processors. So you could for instance run a dual core processor as a single core running Linux, and a single core running bare metal. *THAT* is an awesome concept. But reinventing drivers for a high speed peripheral that already has reallt good drivers is . . . well . . ." don't fix what ain't broke . . " On Thu, Apr 21, 2016 at 5:09 PM, Jordan Yelloz <[email protected]> wrote: > Thanks, that appears to be a pretty small patch, I'll try it out. > I would have no problem using the remoteproc_pruss if it was in the > official kernel but I can't see any as of 4.6-rc4. > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/036b8c05-6fd1-40f5-8bc9-cf554541dd8d%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/036b8c05-6fd1-40f5-8bc9-cf554541dd8d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORqae%3DfVLP214LLz4az6RfEk2KHjJcDWa30fD%3DCTvYOOMw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
