[lkml]   [2000]   [Oct]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Adding vendor drivers...

> So, when a vendor has to add a new driver, especially with the new-style
> makefiles, you have a one-line patch to a makefile, a one-line patch to
> a, and a patch which adds the driver to the tree.
> It would make adding new drivers to vendor kernel packages a whole lot
> easier and more modular if you could add a driver simply by doing:
> cp driver.c driver.mak linux/extras
> ...and then the makefile and config system automatically slurps this
> data. extras/Makefile could look something like:
> style init..
> include *.mak
> style obj-x handling...
> include Rules.make
> Something similar would have to be worked out for
> Of course, for anything complex, patching is still an option.
> Comments? Suggested implementation? :)

Well, having .in and .mak files with single lines in them seems ugly
to me. What about make dep scanning for

/* Makefile: obj-$(CONFIG_MY_DRIVER) += mydriver.o */

in .c files?
I'm "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:39    [W:0.066 / U:3.612 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site