=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 resource hints.
>>> . . .
>>>
>>>
>>>
>>> For reference:
>>>
>>> # find -s / -name GENERIC.hints -print
>>> /usr/src/sys/amd64/conf/GENERIC.hints
>>> /usr/src/sys/i386/conf/GENERIC.hints
>>> /usr/src/sys/powerpc/conf/GENERIC.hints
>>>
>>>
>>> Multiple points:
>>>
>>> ) It seems that aarch64 (arm64?) and armv7 (arm?) have no
>>>=C2=A0 =C2=A0such GENERIC.hints file. The same goes for riscv64=
>>>=C2=A0 =C2=A0(riscv?).
>>>
>>>=C2=A0 =C2=A0The intent for powerpc64 , powerpc64le , and power=
pcspe
>>>=C2=A0 =C2=A0may have the same issue.
>>>
>>>
>>> ) At least for how the local systems were installed, there
>>>=C2=A0 =C2=A0is no such place predefined as /sys/ , not=C2=A0 =
=C2=A0even as a
>>>=C2=A0 =C2=A0symbolic link. "man 7 hier" does not lis=
t such.
>>>
>>>=C2=A0 =C2=A0So it seems /sys -> /usr/src/sys is intended. (=
But
>>>=C2=A0 =C2=A0/usr/src/ need not have been populated, leaving a<=
br>
>>>=C2=A0 =C2=A0lack of any GENERIC.hints in such a case.)
>>>
>>>=C2=A0 =C2=A0Best to not to depend on /sys in the notation show=
n?
>>>
>>>
>>> ) The /ARCH/ reference is unclear vs. MACHINE,
>>>=C2=A0 =C2=A0MACHINE_CPUARCH, and MACHINE_ARCH. The example pat=
hs
>>>=C2=A0 =C2=A0existing for GENERIC.hints do not help because the=
y
>>>=C2=A0 =C2=A0all allow MACHINE =3D=3D MACHINE_CPUARCH ,
>>>=C2=A0 =C2=A0MACHINE =3D=3D MACHINE_ARCH , and
>>>=C2=A0 =C2=A0MACHINE_CPUARCH =3D=3D MACHINE_ARCH. However, base=
d on the
>>>=C2=A0 =C2=A0NOTE paths:
>>
>> Like all things kernel, it's MACHINE.
>>
>>>=C2=A0 =C2=A0# find -s /usr/src/ -name NOTES -print | grep /con=
f/NOTES | more
>>>=C2=A0 =C2=A0/usr/src/sys/amd64/conf/NOTES
>>>=C2=A0 =C2=A0/usr/src/sys/arm/conf/NOTES
>>>=C2=A0 =C2=A0/usr/src/sys/arm64/conf/NOTES
>>>=C2=A0 =C2=A0/usr/src/sys/conf/NOTES
>>>=C2=A0 =C2=A0/usr/src/sys/i386/conf/NOTES
>>>=C2=A0 =C2=A0/usr/src/sys/powerpc/conf/NOTES
>>>=C2=A0 =C2=A0/usr/src/sys/riscv/conf/NOTES
>>>=C2=A0 =C2=A0/usr/src/sys/x86/conf/NOTES
>>>
>>>=C2=A0 =C2=A0None of of the MACHINE* are right: x86 is not one =
of
>>>=C2=A0 =C2=A0any of the 3. Otherwise /arm64/conf/NOTES would su=
ggest
>>>=C2=A0 =C2=A0MACHINE as the only possibility if /ARCH/ was unif=
orm
>>>=C2=A0 =C2=A0for relative to the 3 MACHINE* possibilities. So?:=
>>>
>>>=C2=A0 =C2=A0/usr/src/sys/arm64/conf/GENERIC.hints
>>>=C2=A0 =C2=A0/usr/src/sys/arm/conf/GENERIC.hints
>>>=C2=A0 =C2=A0/usr/src/sys/riscv/conf/GENERIC.hints
>>>
>>>=C2=A0 =C2=A0with no aarch64 , armv7 , powerpc64* , powerpcspe =
, or
>>>=C2=A0 =C2=A0riscv64 examples?
>>
>> We store these in /dev/null these days :).
>>
>> I'll create empty ones for this.
>
>=C2=A0 https://reviews.freebsd.org/D49052
Thanks.
> Just to expand a little: These platforms don't have legacy devices=
> they need to hard-wire in various ways, unlike the other platforms.
> However, people use them to do device instance wiring, so I've cre=
ated
> the empty ones.
An example can also be disabling something that needs to be avoided
for some unusual reason, such as avoiding virtio_gpu under parallels
on aarch64 macOS. (I've not tested doing that yet.)