Re: kern/59276: Detach driver if a module later provides a higher-priority match

["Christoph Badura via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR kern/59276; it has been noted by GNATS.

From: Christoph Badura <bad%bsd.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/59276: Detach driver if a module later provides a
 higher-priority match
Date: Tue, 15 Apr 2025 13:47:16 +0200

 Here's a more convincing example:
 
 I've got an Infinite Noise TRNG that attaches as follows:
 
 uftdi0 at uhub1 port 1 configuration 1 interface 0
 uftdi0: 13-37.org (0x0403) Infinite Noise TRNG (0x6015), rev 2.00/10.00, addr 1
 ucom0 at uftdi0 portno 1
 
 This is because on Linux it uses a daemon process to feed the RNG data
 through a Keccak sponge to /dev/random.
 
 I'd like to have it attach directly in the kernel as a rnd(4) source.
 Hence its match routine would need to return a higher priority than uftdi.
 
 This should work when loaded as a module (if for nothing else than to
 speed up development).
 
 If the uftdi driver gets autoloaded before this device's driver, it shoudl
 be detached when this driver module is loaded.
 
 --chris