Nishant == Nishant Sharma codemarau...@gmail.com writes:
Nishant [...] I never did a clean or dir clean but yes I enabled a
Nishant few packages and modules with new requirements.
Nishant Which is fine by my own thinking. And just for adding
Nishant e.g. batman-adv to existing devices in the
Hi Gui,
this is not supposed to happen though - you can see the magic in
include/kernel-defaults.mk - define Kernel/Configure/Default
The hash is calculated like that:
grep '=[ym]' .../.config | sort | md5sum
Can you diff the Kernel build_dir/target-*/linux-*/linux-*/.config file
before and
Hello members,
Although, I am compiling and using custom OpenWRT images since 8 months
now, but I am still confused with this particular behaviour. I am using
it primarily on x86 Alix APU devices.
Everytime I run a make and kernel gets recompiled, it changes the hex
value appended to the kernel
On Wed, Oct 1, 2014 at 4:13 AM, Nishant Sharma codemarau...@gmail.com wrote:
Although, I am compiling and using custom OpenWRT images since 8 months
now, but I am still confused with this particular behaviour. I am using
it primarily on x86 Alix APU devices.
Everytime I run a make and kernel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/14 14:31, Baptiste Jonglez wrote:
When you activate/deactivate packages in menuconfig, it may modify
what gets compiled into the kernel, to add/remove support for the
various subsystems needed by the packages you build. This will
On 2 October 2014 04:45:38 GMT+05:30, Gui Iribarren g...@altermundi.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/10/14 14:31, Baptiste Jonglez wrote:
When you activate/deactivate packages in menuconfig, it may modify
what gets compiled into the kernel, to add/remove support
