Date: Wed, 29 Apr 2026 23:07:07 +0000 From: Anthony Katernoza <anthony.katernoza@gmail.com> To: freebsd-hackers@freebsd.org Subject: Guidance needed: FreeBSD 15.0-CURRENT Driver attachment for AMD Phoenix SoC Message-ID: <CALzeOLTd-4bFKoHTk2LGwhB-vX4JF5R=QZ1C2s6TZ7dBzXTUxw@mail.gmail.com>
index | next in thread | raw e-mail
[-- Attachment #1 --] Hello, I am seeking support on hardware gaps for the AMD Phoenix SoC. This issue is on a FreeBSD 15.0-CURRENT system. I have AMD drivers on my system that are unmanaged (none@pci). Critically, my FCH LPC Bridge (PCI ID: 1022:790e) is unmanaged. Sensor Fusion (PCI ID: 1022:164a) is also unmanaged. This looks to be an issue in the SoC's newbus hierarchy, as it prevents the kernel from attaching to child devices under FCH, such as the Embedded Controller (EC0). Confirmation of EC0 issues are in the ACPI dump, where the ACPI subsystem comes back as "AE_NOT_FOUND". Furthermore, 9 other related AMD drivers are labeled none@pci. I have already filed a formal bug report, which includes evidence from a compilation of ACPI, dmesg, pciconf & vmstat logs about this issue. FCH, Sensor Fusion, multimedia & other driver results are included: (Aforementioned logs are compiled into an attached .txt file). https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294406 This being said, I am looking for technical assistance on: 1. Whether the problem devices require new chipset drivers or if adding the ID to existing isab(4) or chipset(4) logic is viable. 2. If there are specific testers and/or developers currently working on this type of SoC fabric, who may need raw data from this device. Best regards, Anthony Katernoza [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div>Hello,<br><br></div><span><span><div><span>I am seeking support on hardware gap</span><span>s </span><span>for the AMD Phoenix SoC. <br>This issue is on a FreeBSD 15.0-CURRENT system.<br></span></div><div><span><br></span><span>I have AMD drivers on my system that are unmanaged</span><span> </span><span>(none@pci).<br></span><span><span><div><span>Critically, my FCH LPC Bridge (PCI ID: 1022:790e) is unmanaged.</span></div></span></span>Sensor Fusion (PCI ID: 1022:164a) is also unmanaged.<br><span>This looks to be an issue in the SoC's</span><span> </span><span>newbus hierarchy,<br>as it prevents the kernel from attaching to child</span><span> </span><span>devices under FCH, <br>such as the Embedded Controller (EC0).<br></span></div><div><span>Confirmation of EC0 issues are in the ACPI dump,<br></span></div><div><span>where the ACPI subsystem comes back as "AE_NOT_FOUND".</span></div><div><span>Furthermore, 9 other related AMD drivers are labeled none@pci.<br><br>I have already filed a formal bug report, which includes evidence from</span></div><div><span>a compilation of ACPI, dmesg, pciconf & vmstat logs about this issue.<br></span></div><div><span>FCH, Sensor Fusion, multimedia & other driver results are included:</span></div><div><span><span>(Aforementioned logs are compiled into an attached .txt file).</span></span></div><div><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294406" target="_blank">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294406</a><br><br></div><div>This being said, I am looking for technical assistance on:<br><br></div><div>1. Whether the problem devices require new chipset drivers</div><div>or if adding the ID to existing isab(4) or chipset(4) logic is viable.<br></div><div>2. If there are specific testers and/or developers currently working on <br></div><div>this type of SoC fabric, who may need raw data from this device.<br><br></div><div>Best regards, <br>Anthony Katernoza</div><div><br></div></span></span></div> </div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALzeOLTd-4bFKoHTk2LGwhB-vX4JF5R=QZ1C2s6TZ7dBzXTUxw>