Hi Rich, Here is the update Robert added to his repo yesterday.
https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/393f5ea242a86544063ec2af63ef270094bfa1da/patches/pru/0003-Add-rpmsg_pru-support.patch <https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/393f5ea242a86544063ec2af63ef270094bfa1da/patches/pru/0003-Add-rpmsg_pru-support.patch> Regards, John > On Oct 26, 2015, at 8:50 PM, William Hermans <[email protected]> wrote: > > I have it working Rick on . . . > $ uname -a > Linux beaglebone 4.1.9-bone-rt-r16 #1 Thu Oct 1 06:19:41 UTC 2015 armv7l > GNU/Linux > > This kernel was just an apt-get install. But, it's not a TI specific kernel > if that's what you're wanting. As far as I can tell though, it's identical > except that the pru stuff was re-enabled by Robert at our request some days > ago. Couple weeks maybe ? > > > On Mon, Oct 26, 2015 at 7:29 PM, Rick Mann <[email protected] > <mailto:[email protected]>> wrote: > Hi John, > > Did you ever resolve this? > > > On Oct 19, 2015, at 11:08 , John Syne <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi Rich, > > > > I have this working on BBB using V4.1.6-bone15, but I should receive an x15 > > sometime today and it will take me a few days to do testing. There is > > however one hick-up that needs input from Pantelis to resolve. When BBB > > first boots, remoteproc/virtio_rpmsg_bus load automatically and the PRU > > firmware loads as before. The sample code under samples/rpmsg work work > > perfectly. However, if I uninstall remoteproc.ko and then reinstall it, I > > get a kernel exception. > > > > Investigating further, I found that _omap_device_notifier_call sets > > pdev->archdata.od = NULL when the pruss_remoteproc is uninstalled, but when > > I install the pruss_remoteproc, pruss_probe tries to run > > omap_device_deassert_hardreset which references archdata.od which is is now > > NULL. > > > > Looking at TI’s V3.14 kernel, it does not set archdata.od = NULL, so I can > > uninstall and install the KO without issue. > > > > In the V4.1 code, if I comment out lines 57 & 60 [1], pruss_remoteproc > > uninstalls and installs without error. > > > > My question is how do I recreate archdata.od before pruss_probe executes > > omap_device_deassert_hardreset? Given that this patch was authored by > > Pantelis, I figured you would be the best person to answer my question. > > > > [1] > > https://github.com/RobertCNelson/linux-dev/blob/master/patches/bbb_overlays/0006-arm-omap-Proper-cleanups-for-omap_device.patch > > > > <https://github.com/RobertCNelson/linux-dev/blob/master/patches/bbb_overlays/0006-arm-omap-Proper-cleanups-for-omap_device.patch> > > > > > > Regards, > > John > > > > > > > > > >> On Oct 18, 2015, at 7:11 PM, Robert Nelson <[email protected] > >> <mailto:[email protected]>> wrote: > >> > >> On Sun, Oct 18, 2015 at 8:52 PM, Rick Mann <[email protected] > >> <mailto:[email protected]>> wrote: > >>> > >>>> On Oct 18, 2015, at 17:11 , Robert Nelson <[email protected] > >>>> <mailto:[email protected]>> wrote: > >>>> > >>>> On Sun, Oct 18, 2015 at 7:05 PM, Rick Mann <[email protected] > >>>> <mailto:[email protected]>> wrote: > >>>>> Pruss is still broken in the 4.1.10-ti-r21 kernel, right? > >>>>> > >>>>> Does anyone know if the new remoteproc thing can be used to download > >>>>> existing firmware that was built with pruss in mind, and how I could > >>>>> modify my code to use that instead? > >>>>> > >>>> > >>>> another user got it working with remoteproc, he's just waiting for a > >>>> beta-x15 to arrive so that they will work the same on both boards.. > >>> > >>> Oh, do you remember who that was? > >> > >> Yeap, he will post it when he's ready. > >> > >> Regards, > >> > >> -- > >> Robert Nelson > >> https://rcn-ee.com/ <https://rcn-ee.com/> > >> > >> -- > >> For more options, visit http://beagleboard.org/discuss > >> <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] > >> <mailto:beagleboard%[email protected]>. > >> For more options, visit https://groups.google.com/d/optout > >> <https://groups.google.com/d/optout>. > > > > -- > > For more options, visit http://beagleboard.org/discuss > > <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] > > <mailto:beagleboard%[email protected]>. > > For more options, visit https://groups.google.com/d/optout > > <https://groups.google.com/d/optout>. > > > -- > Rick Mann > [email protected] <mailto:[email protected]> > > > -- > For more options, visit http://beagleboard.org/discuss > <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] > <mailto:beagleboard%[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > For more options, visit http://beagleboard.org/discuss > <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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <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.
