On Wed, Feb 25, 2026 at 06:51:34PM -0600, John G. Heim wrote: > > > Great, but that's not udev's job, that's the kernel's job. Work on > > adding automatic hardware support to the respective drivers as userspace > > isn't involved here as you describe. > > > > Huh... I thought it was the udev system that recognized USB hardware based > on it's ID strings and loaded the appropriate kernel modules. I'm > misinformed then? I mean, clearly you *can* do that in udev, right? I've > already written udev rules to do it. > > I also do not understand your reference to user space. I am about as sure > as I can be that user space is not involved in what I am trying to do.
Yes, udev does load kernel modules based on the USB device ids that the kernel exports. If you know of a way to properly describe speakup devices, then the kernel should be exporting that information so that udev can load speakup with that information. But, from what I have seen, most of these devices just show up as a "generic USB serial device" and so you need the policy of how to determine that it is a speakup device, and that happens in userspace, and should be part of the speakup utils package. thanks, greg k-h
