On Sun, 16 Jan 2005 02:25, Jeremie Le Hen wrote: > I was playing a bit with devd(8) to have ums.ko automatically loaded > when I plug my USB mouse. This works quite well except that it seems > that ums0 is NOT detected when the module is loaded when the mouse is > already plugged. Thus, when I match against the uhid(4) device to get > the ums(4) module loaded, it cannot work since the module is inevitably > loaded after the moused is plugged. > > Is this a bug or a feature ? I've been told that whenever an USB device > is not grabbed by any driver on attach, it uses ugen(4) and it won't be > possible to ``move'' it from ugen(4) to ums(4) later. This is a problem with the USB stack - devices are not reprobed when a new module is loaded. I preload all the USB modules I plan to use (a bit annoying I admit). I believe there is ongoing work in this area though. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:26 UTC