Hi Michael, > No, I suppose I don't have a special reason. I'm running my kernel > without any modules at all, so I was sticking to that. I have it > automated to be easy enough to boot with a new kernel. (As easy as > transferring a new module over and trying it out). > I'm running my test systems with NFS mounted rootfs, so testing a new version of a module doesn't take much more than the bare compile time.
> Could a module mess with the state so that things don't work as > well as a fresh bootup? I do agree that in most cases developing > with modules makes more sense. > If a module cannot be unloaded or behaves differently after reload it most likely did something fishy that you probably would never notice when building the driver into the kernel. Lothar Wassmann ------------------------------------------------------- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
