[enhancement] intel_extreme for 12th Gen Intel / Alder Lake-P integrated graphics controller?

[taos]

Booting via EFI, the integrated graphics of a laptop with an Intel i5-1240P CPU works quite well (and in native resolution) with framebuffer.

However, it's using an Intel Iris Xe Graphics similar to the Intel 11th Gen, so it might be possible to get it recognized by intel_extreme.

listdev indentifies it as:

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
  vendor 8086: Intel Corporation
  device 46a6: Alder Lake-P Integrated Graphics Controller

Here's a syslog excerpt between probing for intel_extreme and deciding on framebuffer (full syslog booting hrev56511 64bit is attached):

KERN: intel_extreme: CALLED status_t init_hardware()
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/usb_rndis
KERN: devfs: "intel_810" api_version missing
KERN: i810: init_hardware() - no supported devices
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/usb_ecm
KERN: ati: init_hardware() - no supported devices
KERN: [33musb_davicom:[0m00.31.116:init_driver::ver.0.9.5
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/usb_davicom
KERN: vesa: init_hardware()
KERN: [33musb_asix:[0m00.31.121:init_driver::ver.0.10.1
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/usb_asix
KERN: framebuffer: init_hardware()
KERN: framebuffer: init_driver()
KERN: framebuffer: publish_devices()
KERN: framebuffer: find_device()
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/framebuffer
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/net/pegasus
KERN: framebuffer find_graphics_card: found base 0x4000000000 size 268435456
KERN: set MTRRs to:
KERN:   mtrr:  0: base: 0x43a00000, size:    0x80000, type: 0
KERN:   mtrr:  1: base: 0x43ac0000, size:    0x20000, type: 0
KERN:   mtrr:  2: base: 0x43af0000, size:     0x8000, type: 0
KERN:   mtrr:  3: base: 0x43ae0000, size:    0x10000, type: 0
KERN:   mtrr:  4: base: 0x43afc000, size:     0x2000, type: 0
KERN:   mtrr:  5: base: 0x43af8000, size:     0x4000, type: 0
KERN:   mtrr:  6: base: 0x60000000, size: 0x20000000, type: 0
KERN:   mtrr:  7: base: 0x80000000, size: 0x80000000, type: 0
KERN:   mtrr:  8: base: 0x4000000000, size: 0x10000000, type: 0
KERN:   mtrr:  9: base: 0x605d1a0000, size:    0x10000, type: 0
KERN: update_mtrrs(): Succeeded setting MTRRs after ignoring uncacheable ranges up to size 0x1000.
KERN: set MTRRs to:
KERN:   mtrr:  0: base: 0x43a00000, size:    0x80000, type: 0
KERN:   mtrr:  1: base: 0x43ac0000, size:    0x20000, type: 0
KERN:   mtrr:  2: base: 0x43af0000, size:     0x8000, type: 0
KERN:   mtrr:  3: base: 0x43ae0000, size:    0x10000, type: 0
KERN:   mtrr:  4: base: 0x43afc000, size:     0x2000, type: 0
KERN:   mtrr:  5: base: 0x43af8000, size:     0x4000, type: 0
KERN:   mtrr:  6: base: 0x60000000, size: 0x20000000, type: 0
KERN:   mtrr:  7: base: 0x80000000, size: 0x80000000, type: 0
KERN:   mtrr:  8: base: 0x4000000000, size: 0x10000000, type: 0
KERN:   mtrr:  9: base: 0x605d1a0000, size:    0x10000, type: 0
KERN: update_mtrrs(): Succeeded setting MTRRs after ignoring uncacheable ranges up to size 0x1000.
KERN: set MTRRs to:
KERN:   mtrr:  0: base: 0x43a00000, size:    0x80000, type: 0
KERN:   mtrr:  1: base: 0x43ac0000, size:    0x20000, type: 0
KERN:   mtrr:  2: base: 0x43af0000, size:     0x8000, type: 0
KERN:   mtrr:  3: base: 0x43ae0000, size:    0x10000, type: 0
KERN:   mtrr:  4: base: 0x43afc000, size:     0x2000, type: 0
KERN:   mtrr:  5: base: 0x43af8000, size:     0x4000, type: 0
KERN:   mtrr:  6: base: 0x60000000, size: 0x20000000, type: 0
KERN:   mtrr:  7: base: 0x80000000, size: 0x80000000, type: 0
KERN:   mtrr:  8: base: 0x605d1a0000, size:    0x10000, type: 0
KERN:   mtrr:  9: base: 0x4000000000, size: 0x10000000, type: 1
KERN: update_mtrrs(): Succeeded setting MTRRs after ignoring uncacheable ranges up to size 0x1000.
KERN: framebuffer: framebuffer_init() completed successfully!
KERN: framebuffer: acc: framebuffer.accelerant

[taos]

syslog booting hrev56511

[korli]

Side xhci question: any reason for such errors?

2022-10-04 23:24:17 KERN: usb error xhci 1: ConfigureEndpoint() failed invalid max_burst_payload
2022-10-04 23:24:17 KERN: usb error xhci 1: unable to configure endpoint: Invalid Argument
2022-10-04 23:24:17 KERN: usb error xhci 1: ConfigureEndpoint() failed invalid max_burst_payload
2022-10-04 23:24:17 KERN: usb error xhci 1: unable to configure endpoint: Invalid Argument

[waddlesplash]

I've seen those but never gotten around to properly investigating. Presumably maxPacketSize is 0, likely reported by the device as such. I didn't try to dig around to see what devices have this problem or determine if we are supposed to define a default or something.