Bumping this. Again. I'd like to *NOT* have to keep supporting the fix for this on the user side in the 5.X series when this really needs to get fixed on the kernel side. I've filed the bug reports. They're just sitting.
In reality, the rpmsg system doesn't really have the hooks to even support the fix from the user side as I can't query the size and depths of the buffers. This needs to get fixed in the PRU rpmsg kernel subsystem. Thanks. On Tuesday, June 30, 2020 at 3:43:01 AM UTC-7 Andrew P. Lentvorski wrote: > So, we're still back at the original question of "Where do I file this bug > so that it gets tracked?" > > I see some recent work on rpmsg bugs at > https://github.com/beagleboard/linux/issues, so I'll file a bug there. > But, is there somewhere else I should file it? > > Thanks. > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/8c22cc26-7c2e-4fc9-a239-db3573efc1ean%40googlegroups.com.
