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
Thanks for the clarification.
On Tue, Aug 16, 2011 at 6:21 PM, 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 mo
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 packa
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
Hi Pawel,
this is an intended behavior of OpenWrt. You should not select something
to be build as an module in "make kernel_menuconfig". all modules should
be build by a kmod package in packages/kernel/modules/. The modules
build in a kmod package are added into the /lib/module/
directory if the p
Hi all,
With the latest trunk version when i used "make kernel_menuconfig" and
enable couple module using "M" to be dynamic i don't see these modules
copying over to /lib/module/2.6.39.2 folder any idea why is not working?
I known this uses to work about 2 years ago.
Thanks,
Pawel
__
