Sorry Rick, I did not mean to Hijack your post, but it seems I've done exactly that . . .
*So.. what would you guys like me to do.. rip out remoteproc_prus so > uio_pruss works again, even thou all of ti's pru tools/wiki are being > updated for remoteproc_pruss.. I currently don't use the 'pruss' system, so > someone will have to maintain it for v4.1.x-ti..* > > *The other option, when remoteproc_pruss doesn't exist just enable > uio_pruss...* > > *Regards,* > Ideally, I'd like to understand the whole process better. Which has nothing to do with wanting you to do anything specific. I really do not know what you have to go through Robert, in order to make everyone happy. I was however imagining *somehow* creating a situation where we could have a *ti* kernel for TI, and a *bone* image to keep things like the PRU's in a working state until we have that other option. From the outside looking in, this seems like something potentially as trivial as a config, and perhaps a different setup script ? I honestly do not know. You tell me. -- 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.
