Robert, On 13/02/19 18:04, Robert Nelson wrote: > Hi Roger, > > On Wed, Feb 13, 2019 at 9:52 AM Roger Quadros <[email protected]> wrote: >> >> Robert, >> >> On 28/01/19 21:15, Robert Nelson wrote: >>> On Mon, Jan 28, 2019 at 12:58 PM Daniel Kulp <[email protected]> wrote: >>>> >>>> >>>> I tried to update our app image from the 4.14 bone kernel to the 4.19 bone >>>> kernel and ran into a big problem: uio_pruss is not configured in as it >>>> is with 4.14. Is this an oversight? Is there anyone I need to contact to >>>> try and convince them to re-enable uio_pruss? I'd like to get >>>> CONFIG_SND_DUMMY also enabled (module) as that would allow us to use some >>>> same configuration between Pi's and BBB's, but that's really minor. >>>> uio_pruss is a must-have. >>>> >>>> The ti kernels also don't have it, but I cannot use the ti kernels due to >>>> other timing reasons. Mostly concerned about the bone kernels right now. >>> >>> Actually, uio_pruss broke in v4.18.x... Congrats's your the first to >>> notice and mention it! ;) >>> >>> Roger @ TI with comments from David posted an RFC for ti's remotproc >>> for mainline.. That's what i have in v4.19.x-bone "today" (and >>> v4.20.x-bone/v5.0.x-bone).. >>
Sorry, I'm still a bit lost here ;). How do I see the PRUSS kernel patches that you have picked up? >> All upstream PRUSS series that I posted will not work without changes in >> the resource tables in pru-software-support packages. >> >> e.g. >> https://github.com/rogerq/pru-software-support-package/commit/6346adba63c1e91414df8f3ea3cd73ccc40d0f2f >> >> If you can wait for 2 weeks then we could have something in >> TI 2019 that should work smoothly. > > So around the time that your first RFC came out, we actually added > that repo by default under /opt/source/ so users could test out your > patchset on the beagle default images: > > https://github.com/RobertCNelson/omap-image-builder/commit/edd84bc5c2d925d67d00d0c2008f48cdd75e3e99 > > So any Stretch/Buster/Bionic image after Nov 24 2018, has your repo > installed by default in the root file system. ;) OK. But I haven't fixed all examples as I wasn't sure if the changes that I'm making will be accepted or not. Suman has insisted that he wants to continue using the old resource table format for TI's 2019 release. What do you think is the best approach to take? I would suggest. -Get PRUSS kernel drivers via ti-linux-4.19.y -Switch pru-software-package to use git://git.ti.com/pru-software-support-package/pru-software-support-package.git Do you see any issues with this? cheers, -roger -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki -- 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/5C644A41.5010105%40ti.com. For more options, visit https://groups.google.com/d/optout.
