> > Frustration subsides immediately when I see some progress. Getting the LKM > in to https://github.com/beagleboard/repos would be a great start. The > folder you mentioned is related to the project tree and uses variables like > PROJ_NAME to fill template files. From my point of view it's better to > fetch the source from the libpruio-lkm package. But Robert should know the > best solution. The libpruio.ko driver is necessary. The file > libpruio-lkm.service can come from package libpruio-lkm, which also adds > the 'pruio' system users group. >
The libpruio.ko module is now wired up into the build process. https://github.com/rcn-ee/libpruio I've got 4.14.69-ti-r76 almost ready to be tagged, so this will be the first test shortly today.. If every works, It should shoot out a "libpruio-modules-4.14.69-ti-r76" deb package. 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYiyYag1kGpOQwcg7S_mZ0Uz%2BMrPRV2pAZGA9USgzUqHRg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
