Isn't this barking up the wrong tree? First of all, WTF amdsmn4)? Apparently there is no man page.
Our autoconfiguration system handles this case just fine with match priorities. That should work for modules too. martin@ noted this in the PR. I recently came into a possession of an Infinite Noise TRNG that attaches as a ucom(4) by default. The to-be-written driver should attach it as a rng device and use match priority to make that happen. So this is a more generic problem that needs solving in the module and autoconfiguration framework. How do you plan to get rid of the script once we've fixed the underlying issues. Your proposed script pampers of the symptoms in a crude way. You can easily use this script locally until the underlying issue(s) have been fixed. On Mon, Apr 07, 2025 at 11:58:13PM -0700, Paul Goyette wrote: > I'd like to commit this within the next few days unless there are > strong reasons against. To be frank: NO! If you still want to commit this, I suggset you get approval by core@ first. --chris
