On Tue, Jan 08, 2002 at 09:04:14AM +0100, Giacomo Catenazzi wrote: > modules.*map exist only on compiled kernel. And entry depends on > architecture and on configuration.
I agree. That's why something like what David has proposed would be more helpful here. > But don't worry. I use the kernel source to find the > MODULES_DEVICE_TABLE (with a partially automated script) to build the > new tables. Do you check for devices that are now handled by different drivers? For example, the CDCEther and acm USB drivers have gone though a series of different configuration changes, where one driver would claim devices meant for the other. It is hopefully all fixes up now, but might have confused your scripts. What about devices that are supported by more than one driver? How do you handle that? (see the USB keyspan_pda and keyspan drivers for an example.) thanks, greg k-h _______________________________________________ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
