90e:169a:b0:650:37e7:e590 with SMTP id
 956f58d0204a3-65c18c4f314mr765267d50.15.1777522058945; Wed, 29 Apr 2026
 21:07:38 -0700 (PDT)
List-Id: Technical discussions relating to FreeBSD <freebsd-hackers.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-hackers
List-Help: <mailto:freebsd-hackers+help@freebsd.org>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Subscribe: <mailto:freebsd-hackers+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-hackers+unsubscribe@freebsd.org>
Sender: owner-freebsd-hackers@FreeBSD.org
MIME-Version: 1.0
From: Anthony Katernoza <anthony.katernoza@gmail.com>
Date: Wed, 29 Apr 2026 23:07:07 +0000
X-Gm-Features: AVHnY4KRvQP7MyNKsXv0QN6olHt2w5TttZ2KTRKI4l_lRL3nLoGmDt7qDNmqdWc
Message-ID: <CALzeOLTd-4bFKoHTk2LGwhB-vX4JF5R=QZ1C2s6TZ7dBzXTUxw@mail.gmail.com>
Subject: Guidance needed: FreeBSD 15.0-CURRENT Driver attachment for AMD
 Phoenix SoC
To: freebsd-hackers@freebsd.org
Content-Type: multipart/alternative; boundary="000000000000e7672e0650a59a2a"
X-Spamd-Result: default: False [-4.97 / 15.00];
	ARC_ALLOW(-1.00)[google.com:s=arc-20240605:i=1];
	NEURAL_HAM_LONG(-1.00)[-0.999];
	NEURAL_HAM_MEDIUM(-1.00)[-0.996];
	NEURAL_HAM_SHORT(-0.97)[-0.972];
	DMARC_POLICY_ALLOW(-0.50)[gmail.com,none];
	R_DKIM_ALLOW(-0.20)[gmail.com:s=20251104];
	R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4864::/56];
	MIME_GOOD(-0.10)[multipart/alternative,text/plain];
	TAGGED_FROM(0.00)[];
	RCVD_TLS_LAST(0.00)[];
	TO_MATCH_ENVRCPT_ALL(0.00)[];
	MIME_TRACE(0.00)[0:+,1:+,2:~];
	RCPT_COUNT_ONE(0.00)[1];
	FREEMAIL_ENVFROM(0.00)[gmail.com];
	FREEMAIL_FROM(0.00)[gmail.com];
	DKIM_TRACE(0.00)[gmail.com:+];
	FROM_HAS_DN(0.00)[];
	DWL_DNSWL_NONE(0.00)[gmail.com:dkim];
	PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org];
	TO_DN_NONE(0.00)[];
	FROM_EQ_ENVFROM(0.00)[];
	MISSING_XM_UA(0.00)[];
	MID_RHS_MATCH_FROMTLD(0.00)[];
	ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US];
	MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org];
	RCVD_COUNT_ONE(0.00)[1];
	RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b136:from]
X-Spamd-Bar: ----
X-Rspamd-Queue-Id: 4g5gcY35NVz3QSB

--000000000000e7672e0650a59a2a
Content-Type: text/plain; charset="UTF-8"

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

--000000000000e7672e0650a59a2a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"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 t=
hat are unmanaged</span><span> </span><span>(none@pci).<br></span><span><sp=
an><div><span>Critically, my FCH LPC Bridge (PCI ID: 1022:790e) is unmanage=
d.</span></div></span></span>Sensor Fusion (PCI ID: 1022:164a) is also unma=
naged.<br><span>This looks to be an issue in the SoC&#39;s</span><span> </s=
pan><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 ar=
e in the ACPI dump,<br></span></div><div><span>where the ACPI subsystem com=
es back as &quot;AE_NOT_FOUND&quot;.</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 &amp; vmstat logs about this issue.<br=
></span></div><div><span>FCH, Sensor Fusion, multimedia &amp; 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=3D"h=
ttps://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D294406" target=3D"_blank=
">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D294406</a><br><br></d=
iv><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 fr=
om this device.<br><br></div><div>Best regards, <br>Anthony Katernoza</div>=
<div><br></div></span></span></div>
</div>

--000000000000e7672e0650a59a2a--