It's also described here: https://groups.google.com/forum/#!searchin/beagleboard/Robert$20Nelson$20remoteproc|sort:date/beagleboard/LOaTgWH7Tpo/T0eote3TAQAJ in John's first post. Which was from Roberts original "how to" post several months back it seems.
On Mon, Nov 7, 2016 at 6:03 PM, William Hermans <[email protected]> wrote: > Yeah, Gregs' working kernel is from before this change. So only had > remoteproc ability. Where these new kernels have the ability to enable > either / or. > > On Mon, Nov 7, 2016 at 5:58 PM, Neil Jubinville <[email protected]> > wrote: > >> Look up in this thread to Robert's post I believe both are disabled. You >> have to choose one and enable it. >> >> On Monday, November 7, 2016 at 5:52:59 PM UTC-7, William Hermans wrote: >>> >>> >>> On Mon, Nov 7, 2016 at 5:39 PM, Greg <[email protected]> wrote: >>> >>>> I didn't adjust anything in the device tree. I never had to do that >>>> before to successfully run the Remoteproc examples. The only thing I have >>>> ever had to tweak is the pull-up/down resistors in the pads. >>>> >>>> When I run lsmod, I am seeing normal Remoteproc drivers after modprobe >>>> commands, except for the rpmsg driver which is not getting inserted when I >>>> think it should. >>>> >>>> I would think there is at least some element of the device tree entries >>>> in /sys which are independent of loadable kernel modules? >>>> I'm trying to understand the approach to debug this type of problem. >>>> I think I need to verify solid device tree entries for the PRUs and go >>>> from there. ??? >>>> >>>> >>> So a while back, in one of the board overlay, or regular overlays, maybe >>> one of the includes( I forget which ) Robert had comments, and commented >>> out code for enabling UIO, or remoteproc in the latest TI kernels. I'm not >>> sure if the newer version of these files have the remoteproc includes >>> commented out or not. So what I'm saying here may not apply. >>> >>> Let me search the groups here and find what I'm thinking of. >>> >> -- >> 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/ms >> gid/beagleboard/58a346dc-09ce-4e54-aa2b-ac48f52275aa%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/58a346dc-09ce-4e54-aa2b-ac48f52275aa%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/CALHSORofVCBhpSwA3Ds%2B2Mzdy%2B5YgcAfkGC%3D%2Bv9Bam8g9QyLxQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
