-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VmxEnable and DebugConsent are now set in Kconfig in upstream cannonlake #10
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jaywalker
changed the title
VmxEnable and DebugConstant are now set in Kconfig in upstream cannonlake
VmxEnable and DebugConsent are now set in Kconfig in upstream cannonlake
May 22, 2019
This is done in the system76_cleanup branch now |
jackpot51
pushed a commit
that referenced
this pull request
Aug 9, 2019
Add VBT 8.0.1038 binary. Panel #10 is modified to support the 1200x1920 LCD panel. This panel is configured as default. LCD and HDMI are working fine. BUG=N/A TEST=booting Facebook FBG1701 Change-Id: If327e4e071df61b02fcec45213c2b700320ef269 Signed-off-by: Frans Hendriks <fhendriks@eltan.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/34446 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Patrick Rudolph <siro@das-labor.org> Reviewed-by: Arthur Heymans <arthur@aheymans.xyz>
jackpot51
pushed a commit
that referenced
this pull request
Sep 26, 2019
EFP1 is configured as 'DisplayPort with HDMI/DVI compatibility'. Using this setting 4K monitor is configured into lower resolution. Change EFP1 setting to 'HDMI/DVI' The next addtional small changes are made in VBT: UEFI GOP Driver Child Device 2 = LFP Child Device 3 = EFP1/LFP LFP Panel configuration Y-Res of Panel #10 = 1920 BUG=N/A TEST=LCD and HDMI on Facebook FBG1701 Change-Id: Idc694b15ff94b83291a8c8252e269b7e6d96f87b Signed-off-by: Frans Hendriks <fhendriks@eltan.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/35043 Reviewed-by: Lance Zhao <lance.zhao@gmail.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
crawfxrd
pushed a commit
that referenced
this pull request
Nov 15, 2021
Update PL1 minimum value from 3W to 12W as per the thermal design discussed in this bug 203371203 comment #10. BUG=b:203371203 BRANCH=None TEST=Build and boot the gimble system Change-Id: Id66cfb6f6dc0217bd4d83eae1d66ad867a1bdb46 Signed-off-by: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/58650 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Scott Chao <scott_chao@wistron.corp-partner.google.com> Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
crawfxrd
added a commit
that referenced
this pull request
May 26, 2022
Based on the constraints for CML. Fixes the following warnings in Linux on system76/oryp8 and system76/gaze16, which have an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A pcieport 0000:00:01.0: can't derive routing for PCI INT B This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack trace on every boot and on S3 suspend. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000fb84c354>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: Ibc968aaa7bf0259879097ff69d2543dcfa2e5e4b Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jun 3, 2022
Based on the constraints for CML. Fixes the following warnings in Linux on system76/oryp8 and system76/gaze16, which have an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A pcieport 0000:00:01.0: can't derive routing for PCI INT B This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack trace on every boot and on S3 suspend. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000fb84c354>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: Ibc968aaa7bf0259879097ff69d2543dcfa2e5e4b Signed-off-by: Tim Crawford <tcrawford@system76.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/64671 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org>
crawfxrd
added a commit
that referenced
this pull request
Jul 29, 2022
Copy the constraints from ADL-S to ADL-P. Fixes the following warning in Linux on System76 oryp9, which has an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack track on every boot. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I550c80105ff861d051170ed748149aeb25a545db Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jul 29, 2022
Copy the constraints from ADL-S to ADL-P. Fixes the following warning in Linux on System76 oryp9, which has an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack track on every boot. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I550c80105ff861d051170ed748149aeb25a545db Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jul 29, 2022
Copy the constraint from ADL-S to ADL-P. Fixes the following warning in Linux on System76 oryp9, which has an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack track on every boot. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I550c80105ff861d051170ed748149aeb25a545db Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jul 29, 2022
Copy the constraints from ADL-S to ADL-P. Fixes the following warning in Linux on System76 oryp9, which has an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack track on every boot. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I550c80105ff861d051170ed748149aeb25a545db Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jul 30, 2022
Copy the constraints from ADL-S to ADL-P. Fixes the following warning in Linux on System76 oryp9, which has an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack track on every boot. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I550c80105ff861d051170ed748149aeb25a545db Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jul 31, 2022
Copy the constraints from ADL-S to ADL-P. Fixes the following warning in Linux on System76 oryp9, which has an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack track on every boot. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I550c80105ff861d051170ed748149aeb25a545db Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Aug 1, 2022
Copy the constraints from ADL-S to ADL-P. Fixes the following warning in Linux on System76 oryp9, which has an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack track on every boot. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I550c80105ff861d051170ed748149aeb25a545db Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Aug 2, 2022
Copy the constraint from ADL-S to ADL-P. Fixes the following warning in Linux on System76 oryp9, which has an NVIDIA GPU on the bridge. pcieport 0000:00:01.0: can't derive routing for PCI INT A This, in turn, resolves an IRQ conflict with the PCH HDA device that would cause a stack track on every boot. irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I550c80105ff861d051170ed748149aeb25a545db Signed-off-by: Tim Crawford <tcrawford@system76.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/66285 Reviewed-by: Tim Wawrzynczak <twawrzynczak@chromium.org> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
crawfxrd
added a commit
that referenced
this pull request
Aug 15, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Aug 15, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Sep 22, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Sep 22, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Sep 26, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Oct 10, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Oct 12, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Oct 17, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Nov 3, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Nov 4, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Nov 4, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Nov 28, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Dec 5, 2022
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jan 4, 2023
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jan 17, 2023
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jan 23, 2023
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Jan 23, 2023
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Nov 17, 2023
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Nov 17, 2023
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Nov 20, 2023
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Feb 16, 2024
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Feb 20, 2024
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
crawfxrd
added a commit
that referenced
this pull request
Feb 20, 2024
Device 0:01.1 does not exist on ADL-P. I assume this works because the bridged device has function 1. Fixes the following error in Linux: pcieport 0000:00:01.0: can't derive routing for PCI INT B snd_hda_intel 0000:01:00.1: PCI INT B: no GSI - using ISA IRQ 10 Which in turn resolves the conflict with the PCH HDA device...again: irq 10: nobody cared (try booting with the "irqpoll" option) <snip> [<00000000bf549647>] azx_interrupt [snd_hda_codec] Disabling IRQ #10 Change-Id: I9d9a0003764a1e031be578c1f406b2a5d7512de7 Signed-off-by: Tim Crawford <tcrawford@system76.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've not yet flashed the result to my darp5 yet, but it builds now (again).