Skip to content
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.

correct firmware path as upstreamed ones #42

Open
vicamo opened this issue Jan 29, 2024 · 7 comments
Open

correct firmware path as upstreamed ones #42

vicamo opened this issue Jan 29, 2024 · 7 comments

Comments

@vicamo
Copy link
Contributor

vicamo commented Jan 29, 2024

In linux-firmware upstream repo commit cfc997c, ivsc firmware blobs are installed into a different path than it is expected now. Need an update to accommodate to the new path.

@wentongwu
Copy link
Contributor

@vicamo IVSC driver set has been upstreamed, could you please use the upsteamed IVSC driver and IPU6 driver? Thanks

@anthonywong
Copy link

@wentongwu I'd like to confirm can mainline kernel today (6.8-rc2 as of this writing) fully replace the ivsc driver in this repo, without any loss of functionalities?
You also mentioned ipu6 driver, but as far as we know, ipu6 driver has not been completely upstreamed yet, could you elaborate on this as well?

@wentongwu
Copy link
Contributor

wentongwu commented Feb 1, 2024

You also mentioned ipu6 driver, but as far as we know, ipu6 driver has not been completely upstreamed yet, could you elaborate on this as well?

I have tested the upstream-ongoing IPU6 driver with upstreamed IVSC driver, it works well. But I don't know the exact progress of IPU6 driver upstreaming, @hao-yao could you please help update current status of IPU6 driver upstreaming? Thanks

@wentongwu
Copy link
Contributor

I learned from @ccgjimlai that, IPU6 driver will make changes accordingly to fit IVSC upstreamed drivers if IPU6 drivers haven't been fully merged to 6.8.

And I suggest that we don't change the path in this repo for previous release compatibility. @vicamo

@wentongwu
Copy link
Contributor

@wentongwu I'd like to confirm can mainline kernel today (6.8-rc2 as of this writing) fully replace the ivsc driver in this repo, without any loss of functionalities?

Yes, the upstreamed IVSC driver can fully replace this repo without any loss of functionalities, but expect according changes from IPU6 github drivers. @anthonywong

@vicamo
Copy link
Contributor Author

vicamo commented Feb 2, 2024

I learned from @ccgjimlai that, IPU6 driver will make changes accordingly to fit IVSC upstreamed drivers if IPU6 drivers haven't been fully merged to 6.8.

And I suggest that we don't change the path in this repo for previous release compatibility. @vicamo

People are running your dkms releases at this moment. If the upstreamed version of IVSC should be used instead from now on, I guess I'll expect a warning on the ivsc-driver README as well as the migration plan, the accommodation changes to ipu6-drivers specifically, being proposed. I did not find there is one such pull request or similar code. Please suggest.

@wentongwu
Copy link
Contributor

wentongwu commented Feb 2, 2024

I learned from @ccgjimlai that, IPU6 driver will make changes accordingly to fit IVSC upstreamed drivers if IPU6 drivers haven't been fully merged to 6.8.
And I suggest that we don't change the path in this repo for previous release compatibility. @vicamo

People are running your dkms releases at this moment. If the upstreamed version of IVSC should be used instead from now on, I guess I'll expect a warning on the ivsc-driver README as well as the migration plan, the accommodation changes to ipu6-drivers specifically, being proposed. I did not find there is one such pull request or similar code. Please suggest.

@ccgjimlai told me Canonical would use IVSC upstream driver for ubuntu 24.04 and IPU6 owner would make the accommodation changes, I don't have much details. @vicamo

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants