openwrt/docs/adding.tex

167 \item kernel sources with patches to make it run on this specific hardware, this does not include binary drivers
186 \item binary drivers linked or to be linked with the shipped kernel version
196 \item make the binary drivers work, until there are open source drivers
232 diff -urN linux-2.x.x/drivers/ linux-2.x.x-modified/drivers > 03-drivers.patch
248 The third patch may contain drivers for: serial console, ethernet NIC, wireless
251 This code might not be useful if you plan on writing drivers from scratch for
290 \subsubsection{Making binary drivers work}
292 As we have explained before, manufacturers do release binary drivers in their GPL
293 tarball. When those drivers are statically linked into the kernel, they become GPL
294 as well, fortunately or unfortunately, most of the drivers are not statically linked.
299 Some drivers require few modifications to be working with your custom kernel,
306 order to make binary drivers work with your custom kernel:
317 \item link binary drivers when possible to the current kernel version
318 \item try to load those binary drivers
322 Most of the time, loading binary drivers will fail, and generate a kernel oops.
323 You can know the last symbol the binary drivers attempted to use, and see in the
326 the stock kernel drivers.
361 \textbf{linux/drivers/mtd/maps/Kconfig}:
372 Then add your source file to the \textbf{linux/drivers/mtd/maps/Makefile}, so
380 \textbf{linux/drivers/mtd/maps/device-flash.c} C source file.
543 with the same directory structure that the kernel uses (e.g: drivers/mtd/maps, arch/mips ..).