Add warning that the PNP info has to follow the module declaration.
Due to how the linker.hints file is laid out, we'll associate the pnp info with the wrong module if the module declaration comes after the pnp info. Until that limiation is removed, we need to have this ordering. Ideally, we'd also enforce the ordering somehow, but I've come up with no way to do that yet...
This commit is contained in:
parent
c8a535291e
commit
f18d106f99
@ -24,7 +24,7 @@
|
||||
.\"
|
||||
.\" $FreeBSD$
|
||||
.\"
|
||||
.Dd October 5, 2018
|
||||
.Dd May 23, 2019
|
||||
.Dt MODULE_PNP_INFO 9
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -196,6 +196,14 @@ MODULE_PNP_INFO("U16:device;D:#;T:vendor=0x1234", pci, my_driver,
|
||||
.Ed
|
||||
.El
|
||||
.\"
|
||||
.Sh BUGS
|
||||
The
|
||||
.Nm
|
||||
macro must follow
|
||||
.Dv DRIVER_MODULE
|
||||
invocations due to limitations in the
|
||||
.Dv linker.hints
|
||||
file format.
|
||||
.Sh SEE ALSO
|
||||
.Xr devmatch 8 ,
|
||||
.Xr DRIVER_MODULE 9 ,
|
||||
|
Loading…
x
Reference in New Issue
Block a user