On 10/09/2016 11:24, Martin Blumenstingl wrote: > On Thu, Sep 8, 2016 at 11:58 PM, Christian Lamparter > <chunk...@googlemail.com> wrote: >> Hello, >> >> On Thursday, September 8, 2016 9:34:07 AM CEST John Crispin wrote: >>> Hi, >>> >>> why is this code located under package/ and not as a kernel patch under >>> target/linux/generic ? > could you please explain why you would prefer that (is your goal to > build it directly into the kernel instead of providing it as module > package)?
having it in the target folder does not mean its builtin. you could add an entry for it in package/kernel/linux/ that will package it for you > >> So yes, if it needs to go in a different location, that would be fine. >> Based on your suggestion, I think the owl-loader.c code can be moved to: >> target/linux/generic/files/drivers/net/wireless/ath9k/owl-loader.c >> >> and the module definition from the Makefile can be copied into: >> package/kernel/linux/modules/wireless.mk > starting with kernel 4.5 you will need to enable > CONFIG_WLAN_VENDOR_ATH and CONFIG_ATH9K_HW in the kernel if you want > it to pick up code from drivers/net/wireless/ath/ath9k/ > > > Regards, > Martin > _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev