Marcus Glocker <[email protected]> wrote: > On Sun, Sep 27, 2020 at 05:57:51PM +0100, Laurence Tratt wrote: > > > On Sun, Sep 13, 2020 at 09:23:36AM +0100, Laurence Tratt wrote: > > > > > Since I recently opened my big fat mouth and suggested that > > > "kern.video.record" (analogous to kern.audio.record) might be a good > > > idea, I > > > decided to put together a quick prototype (heavily based on the > > > kern.audio.record code). This at least roughly works for me but raises > > > some > > > questions such as: > > > > > > * Is uvideo the only driver that can capture video? [I imagine not, but > > > I > > > don't really know.] > > utvfu(4) comes in mind.
And therefore, it makes no sense the diff contains change to uvideo(4) only. I know video(4) is a thin shim, but the blocking logic isn't correctly placed. One more comment. If the bcopy's are skipped, what data is in those buffers? Are they zero'd freshly, or allocated with a M_ZERO type allocation, or what's the story? Or if one toggles the control do the buffers continue to show old records rather than 'black'?
