Intel IPU6 camera support for Dell MayaBay MLK

linux-oem-6.5 builds linux-modules-ipu6-* from ipu6-drivers/mantic, so mantic is also nominated.

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2044991

install this deb fail, seems dkms dependency problem, how to upgrade DKMS or another way to install ipu6?

https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2044991/+files/intel-ipu6-dkms_0~git202310180730.3f813580-0ubuntu0.23.10.2~exp.2_amd64.deb

@kangzhen,

$ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
$ sudo apt install linux-oem-22.04d-exp
$ sudo apt install linux-modules-ipu6-oem-22.04d-exp
$ sudo apt install linux-modules-ivsc-oem-22.04d-exp
$ sudo apt install linux-modules-usbio-oem-22.04d-exp # optional to different platforms

ODM tried to install exp.33 kernel by #4 command and camera still not work.

Attach sosreport.

please don't include upstream changes in debian/changelog. If you are using 'gbp dch' then please remember that it's just a tool, the changelog can be modified to better suit the SRU process (every change needs to have an SRU bug attached to it etc)

Also, no reason to use a packaging version like -0ubuntu0.24.04.x for the devel series, -0ubuntu1 makes more sense

Are these otherwise good for upload? I'll modify the changelogs (-0u0.23.10.2 never got in mantic, for instance) and upload, if so.

@Timo, they're not ready yet. Please hold on.

Attach debdiff for ipu6-drivers & ivsc-driver for mantic and
noble.Need sponsoring.

Re-attached proposed debdiff for ivsc-driver/noble. Remove a redundant line from debian/changelog.

While these debdiff pulls new upstream releases, original tarball is available in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2044991.

uploaded to noble

Could you add some rational of why you prefer to SRU a new version rather than cherrypick selected fixes? The SRU team usually welcome have some more context/something easier to review, in the current form it's hard to tell if the new version includes more changes than what is needed to fix this bug.

This bug was fixed in the package ivsc-driver - 0~git202311021215.73a044d9-0ubuntu1

---------------
ivsc-driver (0~git202311021215.73a044d9-0ubuntu1) noble; urgency=low

  [ You-Sheng Yang ]
  * Intel IPU6 camera support for Dell MayaBay MLK (LP: #2044991)
    - new upstream Release_20231127 release
    - debian: drop patches already included in the upstream release

 -- You-Sheng Yang <email address hidden> Fri, 01 Dec 2023 00:13:52 +0800

This bug was fixed in the package ipu6-drivers - 0~git202311240921.07f0612e-0ubuntu1

---------------
ipu6-drivers (0~git202311240921.07f0612e-0ubuntu1) noble; urgency=medium

  * Intel IPU6 camera support for Dell MayaBay MLK (LP: #2044991)
    - new upstream Release_20231124 release
    - debian: refresh patches

 -- You-Sheng Yang <email address hidden> Sat, 02 Dec 2023 00:45:55 +0800

SRUs are Incomplete per Sebastien's comment. Please also note that "In Progress" for an SRU means "has been uploaded", to quote

> After upload, the bug status should be changed to In Progress

https://wiki.ubuntu.com/StableReleaseUpdates#Staging_an_upload

@Sebastien,

The upstream repository does not have semantic release tags as usually are. The releases they have are more like milestones that mark a certain condition. For the changes between the two releases, there are only 5 commits:

* README: Updated dependencies
* Fix compilation with kernels >= 6.6.0
* ipu6: Fix sensor driver compilation with kernels >= 6.6.0
* media: i2c: Add IVSC handshake support
* media: i2c: Fix coding issues

The thing we must have for this bug are the last two after requested to remove 6.6 compilation support in bug 2026402.

However, in oem projects we're based on the latest LTS, currently 22.04 Jammy, and run a much recent oem kernel, currently oem-6.5 forked from Mantic. As new platforms enabled and features requested, these out-of-tree drivers updates frequently and massively to adopt support for new kernel versions and new hardwares. This, however, becomes a problem that massive changes are always disfavored by stable release team, so ipu6-drivers/jammy will not receive updates necessary for oem-6.5 kernel, but only ipu6-drivers/mantic (before Noble is released) or ipu6-drivers/noble do.

Therefore we're actually compiling linux-modules-{ipu6,ivsc}-oem-22.04.d/jammy with ipu6-drivers, ivsc-driver from Mantic instead of those from Jammy. And ipu6-drivers, ivsc-driver dkms from Jammy do not compile against linux-oem-6.5/jammy, either. Even they do, the supported hardware list is different from that of linux-modules-{ipu6,ivsc}-oem-22.04.d, which is built from dkms packages from Mantic.

And to make things worse, Intel does not keep API/ABI compatibility between kernel and userspace HAL framework. Meaning the userspace HAL must be of the latest release to match the kernel drivers. And we're supposed to have only one copy of userspace HAL in Jammy after those HAL framework being MIRed, which follows we're going to break ancient models once done. Currently those HAL frameworks reside in a separate, per platform, oem archive.

All these messes can only be resolved in one way: to backport the latest drivers dkms packages to Jammy.

With that,

1. linux-modules-{ipu6,ivsc}-oem-22.04.d/jammy can be built from ipu6-drivers/jammy directly,

2. users installed {ipu6-drivers,ivsc-driver}/jammy will get exactly the same thing with linux-modules-{ipu6,ivsc}-oem-22.04.d/jammy,

3. userspace HAL and drivers will always match.

So, here is an attempt to check what will stable release team choose. I would like to end Jammy users' suffering, but I need the admission.