On Monday, January 28, 2019 at 4:40:19 PM UTC-5, Daniel Kulp wrote: > > > > On Monday, January 28, 2019 at 4:20:33 PM UTC-5, Jason Kridner wrote: >> >> On Monday, January 28, 2019 at 1:57:56 PM UTC-5, Daniel Kulp 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. >>> >>> >> For your use case, does it work if CONFIG_SND_DUMMY is added to Robert's >> 4.14-ti builds? >> > > No idea... I've never tried building a kernel for the BBB's. I've always > just relied on the the update_kernel script providing a usable kernel. For > the most part, you guys have done a great job providing kernels that works > for us (or have fixed things we've run into real quick). The lack of > uio_pruss is the first real issue that I'm concerned about. > > The dummy snd device is just "useful" cause a boot time, we can detect if > there isn't a sound device and load the module. Then the rest of the app > can assume there is a sound device available and things "just work". It's > mostly just a nice to have. > > I cannot use the TI kernel as the cpu idle state driver in the TI kernel > really screws up the GPIO0 timing. The bone kernels don't have the idle > states so GPIO0 timing is much more consistent. At some point, I'd like to > dig through the TI kernel stuff to see if there is a way to completely turn > off the cpu idle driver, but haven't had the time. I've used the cpupower > to turn off the various cpuidle states and that helped 95% of the time, but > it's still not as predictable as with the bone kernel. >
So why don't you just ask Robert to add CONFIG_SND_DUMMY to both the older -ti and -bone kernels as we are still using 4.14 for stable stuff for now due to this sort of breakage? A message about the breakage to linux-omap would really be helpful. -- 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/63d20848-8ff3-49f3-a70c-a3ca3e44e918%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
