I think at minimum, It would be good to at least know which config options must be selected, and how they must be selected in order to use the PRUs with current software.
On Mon, Sep 28, 2015 at 3:03 PM, William Hermans <[email protected]> wrote: > *actually PRU uio is only broken in ti's v4.1.x branch.. as the* >> * remoteproc_pruss driver isn't upstream yet, you can renable uio_prus* >> * in v4.1.x-bone/v4.2.x-bone/v4.3.**x-bone i've intentionally disabled >> it* >> * in those branches just so users don't get to use to it..* > > > I'd like a say in that matter myself. e.g. distinctive *bone*, and *ti* > kernels. But I suppose that a kernel config option that can be changed > later to something else ? > > Here is the problem I'm seeing with being forced to move to remoteproc. > Documentation on the web completely sucks. Essentially, it's limited to a > linux/Documentation/*.txt file. Which to me did not seem very informative. > For me though, I tend to understand better if there is a working example. > Setup, and all that. Then I can actually learn as I tinker with this > example, and read the documentation bit by bit. > > In the end, I think remoteproc seems like very cool software technology. > However, if there is limited to no documentation on the subject. Then it > pretty much is useless . . . I've already seen several blog posts > concerning the BBB, and remoteproc. They all seem to be in a holding > pattern, because they can not seem to get things rolling. > > At least with using the PRU the "old way" we actually have something to > work with . . . > > On Mon, Sep 28, 2015 at 2:48 PM, Robert Nelson <[email protected]> > wrote: > >> On Mon, Sep 28, 2015 at 9:44 PM, Rick Mann <[email protected]> wrote: >> > >> >> On Sep 28, 2015, at 11:20 , Robert Nelson <[email protected]> >> wrote: >> >> >> >> On Mon, Sep 28, 2015 at 6:14 PM, Rick Mann <[email protected]> >> wrote: >> >>> Does anyone have an audio cape working in 4.1.x? Would you share your >> specific kernel version, DTBO, and ASLA configurations? >> >> >> >> In v4.1.x-ti this version still doesn't work: >> >> >> >> >> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BONE-AUDI-02-00A0.dts >> >> >> >> I had fixed all the regulator/sound/etc issues, so it does load, but >> >> sound just doesn't come out.. >> >> >> >> I'm out for the rest of the week, so can't test it. >> >> >> >> Does installing v4.3.x-rc fix your audio cape? (for v4.1.x+ we are >> >> using the same cape overlays..) >> >> >> >> sudo apt-get install linux-image-4.3.0-rc3-bone0 >> > >> > I'll try that when I get home. Since PRU UIO is broken past -ti-r10, I >> hadn't considered trying those, but I will. I'm also trying 3.8.13-bone77, >> but having a heck of a time getting all my stuff back-ported (just niggly >> little DT things, capemgr in a different place, etc.). >> >> actually PRU uio is only broken in ti's v4.1.x branch.. as the >> remoteproc_pruss driver isn't upstream yet, you can renable uio_prus >> in v4.1.x-bone/v4.2.x-bone/v4.3.x-bone i've intentionally disabled it >> in those branches just so users don't get to use to it.. >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> >> -- >> 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. >> > > -- 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.
