Sorry for the delay: but this chipset looks to have DDI ports indeed, so that could work. The PLL’s might work differently though.
All in all I expect this to be not a 1:1 fit, but it should be doable if it can be tested.
@Kapix: what do you think about this chipset seeing your research in types? I looked at apollo lake’s Volume 7: Display PDF document. All the others on the ‘01’ site (2016 Intel(R) Processors Based on Apollo Lake Platform (Broxton Graphics) | 01.org) seem to not give more details. Are you able to find more precise and complete register level docs for instance?
In the meantime it became clear that another small update is needed in the driver, it has to let app-server know it does have EDID info in case of laptops, which it does not do yet for internal panels.
Hi, do you have that laptop? In that case can you find the memory controller’s ID? This card is not yet in the driver, though kallisti5 also has a XPS13 (1800p) which -is- detected (But I don’t know it’s IDs yet).
Does the driver (Skylake and it’s a HP PRODESK 600 G2) work with DP? DP did work with the Vesa drive (didn’t thought it would) but now it’s blank (Updated today)
If so, maybe we should re-open it and update it with the latest info. Also please do try to get a syslog from that system. If that won’t work because you cannot make it fully boot, I guess you could do a try on a USB stick, and then after the failed boot, mount that stick on another system running Haiku and grab the syslog from that stick that way?
Interesting: for instance:
no display is detected (which would only make the booticons resolution work at most)
the adpa, etc. register locations are not implemented in your hardware from the looks of it: did not see that behaviour before…