#1 It's not as if Robert doesn't have enough on his plate already. #2 Forcing the need for two different release kernels is not the proper way to go about solving this problem.
So no, the proper solution is not to add more work for Robert. The proper solution is to make the remoteproc project as if it's a working module *NOW*. Loadable module, that can play nice with the rest of the module world. Then mark it as experimental. Worry about the actual remoteproc implementation after that. -- 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/CALHSORp9wmSjfSM2FfRo9CerXd85FGFfgijFpNm9cu81%2BVRM_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
