Re: [pve-devel] [PATCH manager 1/1] api/ui: improve mdev listing for pci mappings

2024-10-30 Thread Thomas Lamprecht
Am 30/10/2024 um 09:42 schrieb Dominik Csapak: > I did not find a way, and AFAICT this parameter is always part of the path, > where we don't can give explicit names Thanks for checking. > Of course, we can leave the name of the parameter the same if you'd > prefer that (with a TODO notice for 9.

Re: [pve-devel] [PATCH manager 1/1] api/ui: improve mdev listing for pci mappings

2024-10-30 Thread Dominik Csapak
On 10/24/24 18:53, Thomas Lamprecht wrote: Am 06/08/2024 um 14:22 schrieb Dominik Csapak: currently when we have a pci resource mapping, we manually check only the available models for the first pci entry. This often works, but not always, since one could have completely different devices in one

Re: [pve-devel] [PATCH manager 1/1] api/ui: improve mdev listing for pci mappings

2024-10-24 Thread Thomas Lamprecht
Am 06/08/2024 um 14:22 schrieb Dominik Csapak: > currently when we have a pci resource mapping, we manually check only > the available models for the first pci entry. This often works, but not > always, since one could have completely different devices in one > mapping, or with the new nvidia sysfs

[pve-devel] [PATCH manager 1/1] api/ui: improve mdev listing for pci mappings

2024-08-06 Thread Dominik Csapak
currently when we have a pci resource mapping, we manually check only the available models for the first pci entry. This often works, but not always, since one could have completely different devices in one mapping, or with the new nvidia sysfs api we don't get the generally available models. To i