Comment 31 for bug 2031412

> Since this includes a new upstream code drop, could you summarize the highlights?

For people are interested in some more readable git history, we have https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/experimental-dkms.

For a quick review here, there have been like a dozen engineering code releases, and they're all one commit code dump without details. For what we can tell, they cover:

1. camera sensor fixes/additions: hm2170, hm2172, gc5035, ov02e10, ov08a10, ov8856, etc.
2. fix build against new kernel releases, inclusive of gpio/V4L2 kernel API changes
3. gpio addition to int3472 for camera sensor controls
4. documentation changes
5. a few changes for the V4L2 interface to ensure a right device number could be chosen
6. support new hardware platform RPL-P, ADL-N, MTL-P
7. support additional V4L2 image format
8. drop test pattern generator
9. new Lattice MIPI aggregator

> Have you inspected them for backwards incompatible changes?

Yes, we tested all released, MIPI camera equipped platforms, TGL & ADL, as commented in the SRU justification.

> Like my comment #24 above, is there a way to test this that does not involve out-of-archive packages? If not, what is the benefit of this update to mantic users?

The PPAs are for easy of verification. In reality you may simply install the dkms or prebuilt linux-modules-{ipu6,ivsc,usbio}-generic packages. General users still need that intel-ipu6 PPA, because it hosts userspace HAL frameworks that are still being MIRed.

> That doesn't sound very reassuring :) Having said that, you think it's ready for a stable release update for mantic users? Mantic users will benefit from this update?

Yes, or they got nothing.

If they're to manually fix IPU6 cameras on their notebook, the same things are mandatory to them, and the same things are only available to them as these are what we can get from Intel.