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/msgid/beagleboard/CALHSORqpZQCzjYtietxntrMuMaT9sirQjfOcwsuPY_cJC2KtTA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
