Thanks that also sounds like a good idea.
On Wed, Aug 17, 2011 at 3:36 AM, Emmanuel Deloget <
emmanuel.delo...@efixo.com> wrote:
> On 08/17/2011 12:21 AM, Hartmut Knaack wrote:
>
>> Hi Hauke,
>> sorry for snatching in.
>>
>>> If you need some kernel module do "make menuconfig" and select it if it
>>> is there or add a module to packages/kernel/modules/.
>>>
>>> Hauke
>>>
>> So what would be the most convenient way to submit changes (i.e.
>> patches) in packages/kernel/modules/ ? This mailing list, or opening a
>> ticket, or anything else? It happened that I created a patch in i2c.mk
>> about 2 months ago and submitted it on june 22nd in this mailing list. I
>> also opened a ticket with the patch attached, about a week later. So far
>> both without any progress. I don't want to be annoying, I know
>> developers are quite busy. Just thought, since you mentioned this topic,
>> I might get a hint how to get such patches applied.
>> Take care
>>
>> Hartmut
>>
>
> Another solution would be to create a modules.mk file in your
> target/linux/${BOARD}/ directory, on the model of the
> package/kernel/module/*.mk files. This file is included when the module
> kernels are to be built.
>
> (and a better solution would be to generate the list of modules from the
> TRISTATE symbols in the kernel config files, but that's a lot harder ; the
> module list changes from one release of Linux to another, and the current
> solution does not work very well ; the problem is then that this list can
> only be built once the kernel has been downloaded and extracted).
>
> Best regards,
>
> -- Emmanuel
>
>
> ______________________________**_________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.**org <openwrt-devel@lists.openwrt.org>
> https://lists.openwrt.org/**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/mailman/listinfo/openwrt-devel>
>
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
