> On Sep 28, 2015, at 16:00 , Robert Nelson <[email protected]> wrote: > > > > On Mon, Sep 28, 2015 at 10:44 PM, William Hermans <[email protected]> wrote: > Yeap... just: > > git clone https://github.com/RobertCNelson/bb-kernel/ > cd bb-kernel/ > git checkout origin/am33x-v4.3 -b tmp > ./build_deb.sh > > (menuconfig loads -> enable uio_pruss) > > copy linux-image*.deb to board, run: sudo dpkg -i linux-image*.deb > then reboot.. > > Thanks for that Robert, it is as easy as I thought it might be - But I was > not sure. As for what ti runs on their kernel, I personally do not care one > way or the other. But I do have a problem with previously working bit and > pieces becoming broken because of it. But I digress, this would be why it > would be refereed to as a "testing branch" I suppose. So far though, I'm > seeing mostly a lot of good in 4.x, and would hate to have to revert to the > "stone age" as it were . . . > > So.. what would you guys like me to do.. rip out remoteproc_prus so > uio_pruss works again, even thou all of ti's pru tools/wiki are being updated > for remoteproc_pruss.. I currently don't use the 'pruss' system, so someone > will have to maintain it for v4.1.x-ti.. > > The other option, when remoteproc_pruss doesn't exist just enable uio_pruss...
I think what you're doing is right, especially for the -ti builds. It's the guys at TI (or anywhere) that make changes that need to ensure old stuff doesn't break, and at the very least make it easy to move to the new thing. That we can reproduce your build to turn off remoteproc and turn on pruss (and hopefully have it work in that case) is probably good enough. -- Rick Mann [email protected] -- 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.
