search for: quirk

If you have any of the devices listed below, please test with a recent -stable or -current. They will stop working in 4.9 and 5.2 although old behavior can _temporarily_ be enabled by adding "options DA_OLD_QUIRKS" to your kernel config. If I don't hear from anyone, they'll be going away permanently after the releases. -Nate #ifdef DA_OLD_QUIRKS /* Below a list of quirks for USB devices supported by umass. */ { /* * This USB floppy drive uses...

Certain combinations of hardware can't actually support the maximum detected speed. Add a quirk list that lists pairs of hostbridge/chip pci ids and the mode that they should work with. See https://bugs.freedesktop.org/show_bug.cgi?id=20341 Reported-by: Jason Detring <detringj at gmail.com> Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I didn't go as far as subde...

...AGP cards but has AGP capability (for the onboard video). At least PC Chips A31G board using this chipset has an AGP-like AGPro slot that's wired to the PCI bus. Enabling AGP will fail (GPU lockup and software fbcon, X11 hangs). Add support for matching just the host bridge in nvkm_device_agp_quirks and add entry for SiS 761 with mode 0 (AGP disabled). Signed-off-by: Ondrej Zary <linux at rainbow-software.org> --- drivers/gpu/drm/nouveau/nvkm/subdev/pci/agp.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pci/agp.c b/...

I've installed CentOS 5.4 on my new Lenovo Ideapad S12 (Atom-based 12" notebook) and need to add a quirk to pm-suspend in order for the laptop to actually go to sleep. There's a couple of quirks that work just fine so I really don't have a preference. I found several instructions but most of them have failed me because CentOS's pm-utils is too ancient. Newer versions come with a parame...

...he stable tag indicates that it's relevant for the following trees: all The bot has tested the following trees: v4.20.8, v4.19.21, v4.14.99, v4.9.156, v4.4.174, v3.18.134. v4.20.8: Build OK! v4.19.21: Failed to apply! Possible dependencies: 01d5d7fa8376 ("PCI: Add macro for Switchtec quirk declarations") v4.14.99: Failed to apply! Possible dependencies: 01d5d7fa8376 ("PCI: Add macro for Switchtec quirk declarations") 06dc4ee54e30 ("PCI: Disable MSI for Freescale Layerscape PCIe RC mode") 07f4f97d7b4b ("vga_switcheroo: Use device link for HDA...

On 10/27/2013 09:54 AM, Ilia Mirkin wrote: > Certain combinations of hardware can't actually support the maximum > detected speed. Add a quirk list that lists pairs of hostbridge/chip pci > ids and the mode that they should work with. > > See https://bugs.freedesktop.org/show_bug.cgi?id=20341 It seems like this quirk is likely too specific. This almost certainly affects more than 5600 Ultra cards and probably not just NV cards...

...all? This is where we get the idea to set 8x AGP from. See > drivers/gpu/drm/nouveau/nvkm/subdev/pci/agp.c for details. The chipset does not support AGP slot but supports AGP for the integrated video. So it shouldn't be completely disabled. > The alternative is to add to nvkm_device_agp_quirks, and just add > something that matches just the host bridge vendor/device, ignoring > the chip. Something like this? diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/pci/agp.c b/drivers/gpu/drm/nouveau/nvkm/subdev/pci/agp.c index 814cb51..385a90f 100644 --- a/drivers/gpu/drm/nouveau/nvkm/s...

...valid if bit 1 is set in VMD > VMLOCK config register 0x70. Future VMDs will also support this feature. > Existing VMDs have config register 0x70 reserved, and will return 0 on > reads. So these shadow registers are simply exposing the host BAR2 & BAR4 addresses into the guest, so the quirk is dependent on reading those values from the device before anyone has written to them and the BAR emulation in the kernel kicks in (not a problem, just an observation). Does the VMD controller code then use these bases addresses to program the bridges/endpoint within the domain? What does the sa...

...a good chance there's a better solution for this (and I'm going to continue investigating for one after sending this patch), this is more just to start a conversation on what the proper way to fix this is. So, I'm kind of confused about why exactly this was implemented as an early boot quirk in the first place. If we're seeing the GPU's PCI device, we already know the GPU is there. Shouldn't we be able to check for the existence of the HDA device once we probe the GPU in nouveau? This would make a lot more sense and be a lot less troublesome. I can see that in the discussio...

Since quirk_nvidia_hda() was added there's now two nvidia device functions on any laptops with nvidia GPUs: the HDA controller, and the GPU itself. Unfortunately this has the sideaffect of breaking quirk_reset_lenovo_thinkpad_50_nvgpu() since pci_reset_function() was using pci_parent_bus_reset() to reset t...

...rn Helgaas <bhelgaas at google.com> Cc: Lukas Wunner <lukas at wunner.de> Cc: linux-pci at vger.kernel.org Cc: nouveau at lists.freedesktop.org Fixes: b516ea586d71 ("PCI: Enable NVIDIA HDA controllers") Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drivers/pci/quirks.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index 44cab813bf951..b10c77bbe4716 100644 --- a/drivers/pci/quirks.c +++ b/drivers/pci/quirks.c @@ -5549,7 +5549,7 @@ static void quirk_nvidia_hda(struct pci_dev *gpu) if (val &...

...ster 0x70. Future VMDs will also support this feature. > > > Existing VMDs have config register 0x70 reserved, and will return 0 on > > > reads. > > > > So these shadow registers are simply exposing the host BAR2 & BAR4 > > addresses into the guest, so the quirk is dependent on reading those > > values from the device before anyone has written to them and the BAR > > emulation in the kernel kicks in (not a problem, just an observation). > It's not expected that there will be anything writing that resource and > those registers are r...

...rk at all. On other systems, including SPARC and PPC64, virtio-pci devices are enumerated as though they are behind an IOMMU, but the virtio host ignores the IOMMU, so we must either pretend that the IOMMU isn't there or somehow map everything as the identity. Add a feature bit to detect that quirk: VIRTIO_F_IOMMU_PLATFORM. Any device with this feature bit set to 0 needs a quirk and has to be passed physical addresses (as opposed to bus addresses) even though the device is behind an IOMMU. Note: it has to be a per-device quirk because for example, there could be a mix of passed-through and...

...rk at all. On other systems, including SPARC and PPC64, virtio-pci devices are enumerated as though they are behind an IOMMU, but the virtio host ignores the IOMMU, so we must either pretend that the IOMMU isn't there or somehow map everything as the identity. Add a feature bit to detect that quirk: VIRTIO_F_IOMMU_PLATFORM. Any device with this feature bit set to 0 needs a quirk and has to be passed physical addresses (as opposed to bus addresses) even though the device is behind an IOMMU. Note: it has to be a per-device quirk because for example, there could be a mix of passed-through and...

This is a note to let you know that I've just added the patch titled clockevents/drivers/i8253: Add support for PIT shutdown quirk to the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: clockevents-drivers-i8253-add-support-for-pit-shutdown-quirk.patch and it can be found in the queue-4.14 subdirectory. If you, or...

This is a note to let you know that I've just added the patch titled clockevents/drivers/i8253: Add support for PIT shutdown quirk to the 4.18-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: clockevents-drivers-i8253-add-support-for-pit-shutdown-quirk.patch and it can be found in the queue-4.18 subdirectory. If you, or...

This is a note to let you know that I've just added the patch titled clockevents/drivers/i8253: Add support for PIT shutdown quirk to the 4.19-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: clockevents-drivers-i8253-add-support-for-pit-shutdown-quirk.patch and it can be found in the queue-4.19 subdirectory. If you, or...

This is a note to let you know that I've just added the patch titled x86/hyper-v: Enable PIT shutdown quirk to the 4.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: x86-hyper-v-enable-pit-shutdown-quirk.patch and it can be found in the queue-4.14 subdirectory. If you, or anyone else, feels it s...

This is a note to let you know that I've just added the patch titled x86/hyper-v: Enable PIT shutdown quirk to the 4.18-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: x86-hyper-v-enable-pit-shutdown-quirk.patch and it can be found in the queue-4.18 subdirectory. If you, or anyone else, feels it s...

This is a note to let you know that I've just added the patch titled clockevents/drivers/i8253: Add support for PIT shutdown quirk to the 4.4-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: clockevents-drivers-i8253-add-support-for-pit-shutdown-quirk.patch and it can be found in the queue-4.4 subdirectory. If you, or an...