Ada
Ada
@seky2205 So, you derived these numbers yourself, from a logic analyzer? Is this a simple replay attack, then? Where did you get the memory location values from?
If I ever have time, I might take a look upstream and make a PR tested against my personal hardware. :)
Woah. Wait a minute, the driver's actually usable?
So you have to modprobe it again? Sounds like the sort of thing a script workaround could fix
There _seems_ to be options for it. [uiMaxNalSize](https://docs.rs/openh264-sys2/latest/openh264_sys2/struct.TagEncParamExt.html#structfield.uiMaxNalSize) and [uiSliceSizeConstraint](https://docs.rs/openh264-sys2/latest/openh264_sys2/struct.SSliceArgument.html#structfield.uiSliceSizeConstraint) exist in upstream codebase, though I'm not exactly sure how to use them. I know certainly that [uiSliceMode](https://docs.rs/openh264-sys2/latest/openh264_sys2/struct.SSliceArgument.html#structfield.uiSliceMode) seems to...
I am getting this same error with GPS enabled.
If the patent was submitted after, we should be good to implement this, yes?