On Fri, 12 Dec 2003 11:15:15 -0500 "Ethan Mattor" <[EMAIL PROTECTED]> wrote:
| Hi all, | | The device I'm developing works nicely, and it is time to write a custom | Linux driver. I've copied the Skeleton driver into the image subdirectory, | and changed the name to 'weasel'. In the usb/image/Kconfig file, I added | the lines: so you have drivers/usb/image/weasel.c ?? | config USB_WEASEL | tristate "New driver from the madman" | depends on USB | help | Say Y here if you've lost your mind. | | Then into the /usb/image/Makefile I added the line: | | obj-$(CONFIG_USB_WEASEL) += weasel.o | | and into file /usb/Makefile: | | obj-$(CONFIG_USB_WEASEL) += image/ I did all of the above and it works for me (since I didn't see any problems with what you had done). | If you haven't guessed by now, I'm a total makefile hack, and am completely | guessing how the Linux kernel system really works. I'm just copying the | format from other files. | | When I run Xconfig the option comes up fine. When I subsequently run make | modules, I get the message: | | No rule to make target 'drivers/usb/image/weasel.c', needed by | 'drivers/usb/image/weasel.o'. Stop. Are you sure you have that source file? | Hmm. I've noticed that a hidden file seems to get produced for each | compiled module, called something like .scanner.o.cmd, however it will not | for my weasel driver. What am I missing? Am I going about the whole | compile operation the hard way? a. Source file according to make b. No. -- ~Randy MOTD: Always include version info. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
