On Mon, Jul 27, 2009 at 04:19:43PM +0400, Denis Borisevich wrote: > 2009/7/27 Belisko Marek <marek.belisko@xxxxxxxxx>: > > Hi, > > > > On Mon, Jul 27, 2009 at 1:13 PM, Denis Borisevich<dennisfen@xxxxxxxxx> wrote: > >> Hi! > >> I have driver for PCI serial board, it compiles as a module, loads and > >> works fine. Now it exists as a several files outside the kernel source > >> tree. I want to integrate this code within the kernel source tree: I > >> want it to exist as some files inside the kernel source, I want to be > >> able to select this driver in kernel config and so on. So can any one > >> provide me any instructions to achieve this task (I hope it is not > >> very difficult) or point to any online documents, etc.? > > Just read: > > http://lxr.linux.no/linux+v2.6.30/Documentation/SubmittingDrivers > > or you can post you files (patches) to Greg K-H (greg@xxxxxxxxx) and > > he will put it to > > staging directory in linux-next tree. Your driver will be after some > > cleanups and rewiews > > put to main kernel tree hopefully. > > Thank you for reply but I think you got me wrong. I don't want to > submit my driver to mainline kernel. I just want to integrate it with > my local kernel source tree for personal use. Then add a few lines to the specific Kconfig file where your driver lives in the kernel tree, adding the config option for the driver, and a single line to the relevant Makefile adding the driver to the build. For example, if your driver is called foo, you could add this to the Kconfig file: config FOO tristate "Foo device support" depends on PCI help This driver support the foo device and then in the Makefile add the line: $(CONFIG_FOO) += foo.o Have you tried that? Do you have a pointer to your driver / patch? thanks, greg k-h -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
