New device IDs for Intel Raptor Lake S platform
Bug #1982749 reported by
You-Sheng Yang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
| linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Jammy |
Won't Fix
|
Undecided
|
Unassigned | ||
| Kinetic |
Won't Fix
|
Undecided
|
Unassigned | ||
| linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Jammy |
Won't Fix
|
Undecided
|
Unassigned | ||
| Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
| linux-oem-6.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
| Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
[Feature Description]
This task is to identify what new device IDs are required for RPL-S.
Placeholder for RPL-S IDs that should be published.
USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6
SMBus 0x7a23 9c02d4011e92 v5.18-rc1
I²C 0x7a4c 0x7a4d 0x7a4e 0x7a4f 0x7a7c 0x7a7d 8c70bd5802f4 v5.18-rc1
HS-UART 0x7a28 0x7a29 0x7a5c 0x7a7e 8c70bd5802f4 v5.18-rc1
SPI 0x7a2a 0x7a2b 0x7a79 0x7a7b 8c70bd5802f4 v5.18-rc1
SPI Flash Controller 0x7a24 299d8b74519d v5.18-rc4
GPIO INTC1085 ddfdd1304e59 v5.18-rc1
NPK 0x7a26 23e2de5826e2f v6.0-rc1
NPK/CPU 0xA76Fh ff46a601afc5a v6.0-rc1
TBT
AHCI Binds by PCI Class
XHCI Binds by PCI Class
| tags: | added: intel oem-priority originate-from-1960931 |
| description: | updated |
Revision history for this message
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Missing required logs. | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| description: | updated |
| description: | updated |
| Changed in linux (Ubuntu Jammy): | |
| status: | New → Won't Fix |
| Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
| status: | New → Invalid |
Revision history for this message
| You-Sheng Yang (vicamo) wrote | #2 |
| Changed in linux-oem-5.17 (Ubuntu Jammy): | |
| status: | New → Incomplete |
Revision history for this message
| Timo Aaltonen (tjaalton) wrote | #3 |
| Changed in linux-oem-6.0 (Ubuntu Kinetic): | |
| status: | New → Invalid |
| Changed in linux-oem-6.0 (Ubuntu Jammy): | |
| status: | New → Incomplete |
| description: | updated |
| Changed in linux-oem-6.0 (Ubuntu Jammy): | |
| status: | Incomplete → Fix Released |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Fix Released |
| Changed in linux (Ubuntu Kinetic): | |
| status: | Incomplete → Won't Fix |
| Changed in hwe-next: | |
| status: | New → Fix Released |
| Changed in linux-oem-5.17 (Ubuntu Jammy): | |
| status: | Incomplete → Won't Fix |
To post a comment you must log in.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1982749
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.